Irbe Krumina 05093ea7d9 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>		2024-01-09 14:13:22 +00:00
..
apis	cmd/k8s-operator,k8s-operator: allow the operator to deploy exit nodes via Connector custom resource (#10724)	2024-01-09 14:13:22 +00:00
conditions_test.go	cmd/k8s-operator: operator can create subnetrouter (#9505)	2023-12-14 13:51:59 +00:00
conditions.go	cmd/k8s-operator: operator can create subnetrouter (#9505)	2023-12-14 13:51:59 +00:00