mirror of
https://github.com/tailscale/tailscale.git
synced 2024-11-26 19:45:35 +00:00
a6cc2fdc3e
* 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>
41 lines
1.1 KiB
YAML
41 lines
1.1 KiB
YAML
# This file is not a complete manifest, it's a skeleton that the operator embeds
|
|
# at build time and then uses to construct Tailscale proxy pods.
|
|
apiVersion: apps/v1
|
|
kind: StatefulSet
|
|
metadata: {}
|
|
spec:
|
|
replicas: 1
|
|
template:
|
|
metadata:
|
|
deletionGracePeriodSeconds: 10
|
|
spec:
|
|
serviceAccountName: proxies
|
|
initContainers:
|
|
- name: sysctler
|
|
securityContext:
|
|
privileged: true
|
|
command: ["/bin/sh"]
|
|
args:
|
|
- -c
|
|
- sysctl -w net.ipv4.ip_forward=1 net.ipv6.conf.all.forwarding=1
|
|
resources:
|
|
requests:
|
|
cpu: 1m
|
|
memory: 1Mi
|
|
containers:
|
|
- name: tailscale
|
|
imagePullPolicy: Always
|
|
env:
|
|
- name: TS_USERSPACE
|
|
value: "false"
|
|
- name: TS_AUTH_ONCE
|
|
value: "true"
|
|
- name: POD_IP
|
|
valueFrom:
|
|
fieldRef:
|
|
fieldPath: status.podIP
|
|
securityContext:
|
|
capabilities:
|
|
add:
|
|
- NET_ADMIN
|