diff options
| author | Irbe Krumina <irbe@tailscale.com> | 2023-12-14 13:51:59 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-12-14 13:51:59 +0000 |
| commit | 1a08ea5990c30caef5ad2c207c7e9ff2a94e8859 (patch) | |
| tree | 71d77fbcf722834c033ba060a289aca9b4006edf /control/controlknobs | |
| parent | b62a3fc89535756de2aa05ee3f298ef563bdbd34 (diff) | |
| download | tailscale-1a08ea5990c30caef5ad2c207c7e9ff2a94e8859.tar.xz tailscale-1a08ea5990c30caef5ad2c207c7e9ff2a94e8859.zip | |
cmd/k8s-operator: operator can create subnetrouter (#9505)
* k8s-operator,cmd/k8s-operator,Makefile,scripts,.github/workflows: add Connector kube CRD.
Connector CRD allows users to configure the Tailscale Kubernetes operator
to deploy a subnet router to expose cluster CIDRs or
other CIDRs available from within the cluster
to their tailnet.
Also adds various CRD related machinery to
generate CRD YAML, deep copy implementations etc.
Engineers will now have to run
'make kube-generate-all` after changing kube files
to ensure that all generated files are up to date.
* cmd/k8s-operator,k8s-operator: reconcile Connector resources
Reconcile Connector resources, create/delete subnetrouter resources in response to changes to Connector(s).
Connector reconciler will not be started unless
ENABLE_CONNECTOR env var is set to true.
This means that users who don't want to use the alpha
Connector custom resource don't have to install the Connector
CRD to their cluster.
For users who do want to use it the flow is:
- install the CRD
- install the operator (via Helm chart or using static manifests).
For Helm users set .values.enableConnector to true, for static
manifest users, set ENABLE_CONNECTOR to true in the static manifest.
Updates tailscale/tailscale#502
Signed-off-by: Irbe Krumina <irbe@tailscale.com>
Diffstat (limited to 'control/controlknobs')
0 files changed, 0 insertions, 0 deletions