Do we want to allow pods to talk to pcluster apiservers?

[ncdc]

Is your feature request related to a problem? Please describe.
Pre-kcp, when I write a controller and deploy it as a pod (via a deployment) to my cluster, it typically talks to kubernetes.default.svc using in-cluster config to communicate with the apiserver (e.g. to manipulate CRs).

Post-kcp, when I apply a deployment to kcp, the resulting pod(s) run in a physical cluster, but we want them talking to the kcp apiserver to perform operations against CRs and whatnot. If we don't do anything, when the pod resolves kubernetes.default.svc, it is for the physical cluster. The pod won't be able to see the CRs in the kcp apiserver because of this.

The above is covered by #280

Rescoping this to ask: do we want to allow pods to talk to pcluster apiservers? If so, how?

Describe the solution you'd like
Assuming we want to, figure out how to handle pods talking to pcluster apiservers:

1. Pod wants to manipulate CRs
   1. Needs DNS for kubernetes service to resolve to KCP?
   2. Needs env vars for kubernetes to resolve to KCP?
   3. Needs SA token from kcp namespace injected into pod in physical cluster
2. Pod wants to talk to physical cluster apiserver
   1. Is this a valid use case?
   2. If so, what permissions (SA token) does it use?
   3. Does it use DNS? env vars?

[ncdc]

Rescoping to just case 2 - "pod wants to talk to physical cluster apiserver" as case 1 is handled by #280

[sttts]

I don't see how this is a valid use-case. Why would one want to talk to a pcluster, and why isn't that something outside of the standard TMC flow?

[ncdc]

Agreed, closing