You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
tailscale/cmd/k8s-operator/deploy
David Bond 12ad630128
cmd/k8s-operator: allow specifying replicas for connectors (#16721)
This commit adds a `replicas` field to the `Connector` custom resource that
allows users to specify the number of desired replicas deployed for their
connectors.

This allows users to deploy exit nodes, subnet routers and app connectors
in a highly available fashion.

Fixes #14020

Signed-off-by: David Bond <davidsbond93@gmail.com>
3 months ago
..
chart cmd/{k8s-operator,k8s-proxy}: add kube-apiserver ProxyGroup type (#16266) 5 months ago
crds cmd/k8s-operator: allow specifying replicas for connectors (#16721) 3 months ago
examples cmd/{containerboot,k8s-operator},k8s-operator,kube: add ProxyGroup controller (#13684) 1 year ago
manifests cmd/k8s-operator: allow specifying replicas for connectors (#16721) 3 months ago
README.md cmd/k8s-operator: generate static kube manifests from the Helm chart. (#10436) 2 years ago

README.md

Tailscale Kubernetes operator deployment manifests

./cmd/k8s-operator/deploy contain various Tailscale Kubernetes operator deployment manifests.

Helm chart

./cmd/k8s-operator/deploy/chart contains Tailscale operator Helm chart templates. The chart templates are also used to generate the static manifest, so developers must ensure that any changes applied to the chart have been propagated to the static manifest by running go generate tailscale.com/cmd/k8s-operator

Static manifests

./cmd/k8s-operator/deploy/manifests/operator.yaml is a static manifest for the operator generated from the Helm chart templates for the operator.