mirror of
https://github.com/tailscale/tailscale.git
synced 2025-08-17 11:37:19 +02:00
4dfed6b146
Adds a new k8s-proxy command to convert operator's in-process proxy to
a separately deployable type of ProxyGroup: kube-apiserver. k8s-proxy
reads in a new config file written by the operator, modelled on tailscaled's
conffile but with some modifications to ensure multiple versions of the
config can co-exist within a file. This should make it much easier to
support reading that config file from a Kube Secret with a stable file name.
To avoid needing to give the operator ClusterRole{,Binding} permissions,
the helm chart now optionally deploys a new static ServiceAccount for
the API Server proxy to use if in auth mode.
Proxies deployed by kube-apiserver ProxyGroups currently work the same as
the operator's in-process proxy. They do not yet leverage Tailscale Services
for presenting a single HA DNS name.
Updates #13358
Change-Id: Ib6ead69b2173c5e1929f3c13fb48a9a5362195d8
Signed-off-by: Tom Proctor <tomhjp@users.noreply.github.com>
|
||
|---|---|---|
| .. | ||
| apiserverproxy-rbac.yaml | ||
| deployment.yaml | ||
| ingressclass.yaml | ||
| NOTES.txt | ||
| oauth-secret.yaml | ||
| operator-rbac.yaml | ||
| proxy-rbac.yaml | ||