mirrors/tailscale
1
0
Fork 0
Code Issues Pull Requests Projects Wiki Activity
041622c92f
tailscale/cmd/k8s-operator/deploy
History
Tom Proctor 3adad364f1
cmd/k8s-operator,k8s-operator: include top-level CRD descriptions (#14435) 
When reading https://doc.crds.dev/github.com/tailscale/tailscale/tailscale.com/ProxyGroup/v1alpha1@v1.78.3
I noticed there is no top-level description for ProxyGroup and Recorder. Add
one to give some high-level direction.

Updates #cleanup

Change-Id: I3666c5445be272ea5a1d4d02b6d5ad4c23afb09f

Signed-off-by: Tom Proctor <tomhjp@users.noreply.github.com>
2024-12-20 16:12:56 +00:00
..
chart cmd/k8s-operator/deploy/chart: allow reading OAuth creds from a CSI driver's volume and annotating operator's Service account (#14264) 2024-12-03 17:00:40 +00:00
crds cmd/k8s-operator,k8s-operator: include top-level CRD descriptions (#14435) 2024-12-20 16:12:56 +00:00
examples cmd/{containerboot,k8s-operator},k8s-operator,kube: add ProxyGroup controller (#13684) 2024-10-07 14:58:45 +01:00
manifests cmd/k8s-operator,k8s-operator: include top-level CRD descriptions (#14435) 2024-12-20 16:12:56 +00:00
README.md cmd/k8s-operator: generate static kube manifests from the Helm chart. (#10436) 2023-12-04 10:18:07 +00:00

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.