Another thing to be mindful of is the service account token that each pod gets. While these rarely have access to the entire cluster, it is relatively easy to

Another thing to be mindful of is the service account token that each pod gets. While these rarely have access to the entire cluster, it is relatively easy to configure an application to bridge HTTP requests to the API server, which would be a minor disaster. (I noticed this while writing a small Envoy control plane. Everything exists in my config format to pick up the TLS certificates that the Envoy pod already has to create a backend that points to your API server, automatically giving any HTTP requests routed to that backend the credentials of the Envoy pod itself. Add a route in the route table, and now you have a publicly-available route to your API server. You would have to go out of your way to do this, but it's something to keep in mind -- pods have more privileges than just "run the program in the container".)