Irbe Krumina a6cc2fdc3e 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>		2024-02-08 06:45:42 +00:00
..
templates	cmd/k8s-operator: generate static kube manifests from the Helm chart. (#10436)	2023-12-04 10:18:07 +00:00
authproxy-rbac.yaml	cmd/k8s-operator: allow to install operator via helm (#9920)	2023-10-30 18:18:09 +00:00
operator.yaml	cmd/k8s-operator/deploy: allow modifying operator tags via Helm values	2024-01-19 21:22:23 +00:00
proxy.yaml	cmd/{containerboot,k8s-operator/deploy/manifests}: optionally allow proxying cluster traffic to a cluster target via ingress proxy (#11036)	2024-02-08 06:45:42 +00:00
userspace-proxy.yaml	cmd/k8s-operator: allow to install operator via helm (#9920)	2023-10-30 18:18:09 +00:00