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
Irbe Krumina c59ab6baac
cmd/k8s-operator/deploy: ensure that operator can write kube state Events (#14177)
A small follow-up to #14112- ensures that the operator itself can emit
Events for its kube state store changes.

Updates tailscale/tailscale#14080

Signed-off-by: Irbe Krumina <irbe@tailscale.com>
18 hours ago
..
chart cmd/k8s-operator/deploy: ensure that operator can write kube state Events (#14177) 18 hours ago
crds cmd/k8s-operator,k8s-operator,kube/kubetypes: add an option to configure app connector via Connector spec (#13950) 2 weeks ago
examples cmd/{containerboot,k8s-operator},k8s-operator,kube: add ProxyGroup controller (#13684) 2 months ago
manifests cmd/k8s-operator/deploy: ensure that operator can write kube state Events (#14177) 18 hours ago
README.md cmd/k8s-operator: generate static kube manifests from the Helm chart. (#10436) 12 months 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.