mirror of
https://github.com/tailscale/tailscale.git
synced 2024-11-26 19:45:35 +00:00
303125d96d
Containerboot container created for operator's ingress and egress proxies are now always configured by passing a configfile to tailscaled (tailscaled --config <configfile-path>. It does not run 'tailscale set' or 'tailscale up'. Upgrading existing setups to this version as well as downgrading existing setups at this version works. Updates tailscale/tailscale#10869 Signed-off-by: Irbe Krumina <irbe@tailscale.com>
39 lines
1018 B
YAML
39 lines
1018 B
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: POD_IP
|
|
valueFrom:
|
|
fieldRef:
|
|
fieldPath: status.podIP
|
|
securityContext:
|
|
capabilities:
|
|
add:
|
|
- NET_ADMIN
|