diff options
| author | Irbe Krumina <irbe@tailscale.com> | 2024-01-09 14:13:22 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-01-09 14:13:22 +0000 |
| commit | 05093ea7d92277290768f0acaa4208e7766e2507 (patch) | |
| tree | aeba896da48240ac534292c4e3b7a1c717ce1913 /util/execqueue/execqueue.go | |
| parent | 953fa80c6f466b8c3ffe7ba3a97dd1ae8e5f6bfe (diff) | |
| download | tailscale-05093ea7d92277290768f0acaa4208e7766e2507.tar.xz tailscale-05093ea7d92277290768f0acaa4208e7766e2507.zip | |
cmd/k8s-operator,k8s-operator: allow the operator to deploy exit nodes via Connector custom resource (#10724)
cmd/k8s-operator/deploy/crds,k8s-operator/apis/v1alpha1: allow to define an exit node via Connector CR.
Make it possible to define an exit node to be deployed to a Kubernetes cluster
via Connector Custom resource.
Also changes to Connector API so that one Connector corresponds
to one Tailnet node that can be either a subnet router or an exit
node or both.
The Kubernetes operator parses Connector custom resource and,
if .spec.isExitNode is set, configures that Tailscale node deployed
for that connector as an exit node.
Signed-off-by: Irbe Krumina <irbe@tailscale.com>
Co-authored-by: Anton Tolchanov <anton@tailscale.com>
Diffstat (limited to 'util/execqueue/execqueue.go')
0 files changed, 0 insertions, 0 deletions