mirror of
https://github.com/tailscale/tailscale.git
synced 2024-11-26 19:45:35 +00:00
05093ea7d9
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>
20 lines
641 B
YAML
20 lines
641 B
YAML
# Before applying ensure that the operator owns tag:prod.
|
|
# https://tailscale.com/kb/1236/kubernetes-operator/#setting-up-the-kubernetes-operator.
|
|
# To set up autoapproval set tag:prod as approver for 10.40.0.0/14 route and exit node.
|
|
# Otherwise approve it manually in Machines panel once the
|
|
# ts-prod Tailscale node has been created.
|
|
# See https://tailscale.com/kb/1018/acls/#auto-approvers-for-routes-and-exit-nodes
|
|
apiVersion: tailscale.com/v1alpha1
|
|
kind: Connector
|
|
metadata:
|
|
name: prod
|
|
spec:
|
|
tags:
|
|
- "tag:prod"
|
|
hostname: ts-prod
|
|
subnetRouter:
|
|
advertiseRoutes:
|
|
- "10.40.0.0/14"
|
|
- "192.168.0.0/14"
|
|
exitNode: true
|