diff options
| author | Irbe Krumina <irbe@tailscale.com> | 2024-02-08 06:45:42 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-02-08 06:45:42 +0000 |
| commit | a6cc2fdc3e2645a6931c128f8e8f716680e968b0 (patch) | |
| tree | 8aabdd5508ca61975507e2428d7f51907c414366 /control/controlknobs/controlknobs_test.go | |
| parent | 2404b1444e823b90f0599734492d7375f5bf05db (diff) | |
| download | tailscale-a6cc2fdc3e2645a6931c128f8e8f716680e968b0.tar.xz tailscale-a6cc2fdc3e2645a6931c128f8e8f716680e968b0.zip | |
cmd/{containerboot,k8s-operator/deploy/manifests}: optionally allow proxying cluster traffic to a cluster target via ingress proxy (#11036)
* cmd/containerboot,cmd/k8s-operator/deploy/manifests: optionally forward cluster traffic via ingress proxy.
If a tailscale Ingress has tailscale.com/experimental-forward-cluster-traffic-via-ingress annotation, configure the associated ingress proxy to have its tailscale serve proxy to listen on Pod's IP address. This ensures that cluster traffic too can be forwarded via this proxy to the ingress backend(s).
In containerboot, if EXPERIMENTAL_PROXY_CLUSTER_TRAFFIC_VIA_INGRESS is set to true
and the node is Kubernetes operator ingress proxy configured via Ingress,
make sure that traffic from within the cluster can be proxied to the ingress target.
Updates tailscale/tailscale#10499
Signed-off-by: Irbe Krumina <irbe@tailscale.com>
Diffstat (limited to 'control/controlknobs/controlknobs_test.go')
0 files changed, 0 insertions, 0 deletions