opened
dadjeibaah
username_0
This PR moves the tap service to its own pod in the control plane in order to lay the foundation to authorize tap requests using Kubernetes' APIExtension API. This PR makes tap work the same way it already does currently, however, this PR adds a new HTTPS server in the tap service that will eventually be used to authorize tap requests. 

In a follow up PR, the new HTTPS server will eventually set up a Tap CRD with the server registering itself to allow it to work with Kubernetes aggregation layer.

Relates #2712
Move tap service into its own pod.
issue
created
dadjeibaah
username_0
@siggy thanks for the insight on this change, you bring up a good point on making sure this still works on upgrade. I would have to think a little bit in making sure that there is some fallback in the follow-up PR for the CLI when we try to tap resources.

In the meantime, I think this PR is safe to merge once I address all your comments and the failing tests.
comment