mirror of
https://github.com/tailscale/tailscale.git
synced 2026-09-13 14:29:49 -04:00
The PeerRelay resource hardcoded UDP port 41641 in the generated Service, the tailscaled config, status.endpoints and the advertised static endpoints. That breaks deployments where the load balancer address or port is not what peers can actually reach, e.g. behind NAT. Add spec.service.port to choose the UDP port, and spec.staticEndpoints to advertise extra address:port pairs alongside the discovered load balancer endpoints. A replica whose only endpoint is a static one counts as addressed, and a static entry's port wins when it names an address the load balancer already provides. The e2e tests now supply static endpoints, which lets them assert the PeerRelayReady condition goes True in kind, where no cloud controller ever gives the LoadBalancer Services an address. Fixes #20821 Change-Id: I463012cd447c81c2849fa653fa18eb82662aaf4f Signed-off-by: David Bond <davidsbond93@gmail.com>
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.