mirror of
https://github.com/tailscale/tailscale.git
synced 2026-11-22 04:32:40 +09:00
Proxies now serve /livez and /readyz, but nothing points Kubernetes probes at them. This adds livenessProbe and readinessProbe fields to the ProxyClass Tailscale container, each off unless set, with tunable timing (older proxy images don't serve the endpoints, so a probe would fail against them), and wires them into ProxyGroup proxies. A ProxyGroup is rejected if its ProxyClass sets probes but its env would leave the endpoints unreachable, such as TS_ENABLE_HEALTH_CHECK=false, TS_LOCAL_ADDR_PORT on loopback, or the deprecated TS_HEALTHCHECK_ADDR_PORT. Probes follow a custom TS_LOCAL_ADDR_PORT port, and liveness gets a 5s timeout by default, as a restart drops traffic that a slow tailscaled still carries. Updates tailscale/corp#38175 Signed-off-by: chaosinthecrd <tom@tmlabs.co.uk>
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.