docs/k8s: Use TS_AUTHKEY instead of TS_AUTH_KEY (#7092)

Updates https://github.com/tailscale/tailscale-www/issues/2199.

Signed-off-by: Walter Poupore <walterp@tailscale.com>
This commit is contained in:
Walter Poupore 2023-01-27 15:05:03 -08:00 committed by GitHub
parent 50da265608
commit 11f7f7d4a0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 9 additions and 9 deletions

View File

@ -16,7 +16,7 @@ There are quite a few ways of running Tailscale inside a Kubernetes Cluster, som
metadata:
name: tailscale-auth
stringData:
TS_AUTH_KEY: tskey-...
TS_AUTHKEY: tskey-...
```
1. Tailscale (v1.16+) supports storing state inside a Kubernetes Secret.

View File

@ -33,11 +33,11 @@ spec:
value: "{{TS_KUBE_SECRET}}"
- name: TS_USERSPACE
value: "false"
- name: TS_AUTH_KEY
- name: TS_AUTHKEY
valueFrom:
secretKeyRef:
name: tailscale-auth
key: TS_AUTH_KEY
key: TS_AUTHKEY
optional: true
- name: TS_DEST_IP
value: "{{TS_DEST_IP}}"

View File

@ -19,11 +19,11 @@ spec:
value: "{{TS_KUBE_SECRET}}"
- name: TS_USERSPACE
value: "false"
- name: TS_AUTH_KEY
- name: TS_AUTHKEY
valueFrom:
secretKeyRef:
name: tailscale-auth
key: TS_AUTH_KEY
key: TS_AUTHKEY
optional: true
securityContext:
capabilities:

View File

@ -19,11 +19,11 @@ spec:
value: "{{TS_KUBE_SECRET}}"
- name: TS_USERSPACE
value: "true"
- name: TS_AUTH_KEY
- name: TS_AUTHKEY
valueFrom:
secretKeyRef:
name: tailscale-auth
key: TS_AUTH_KEY
key: TS_AUTHKEY
optional: true
- name: TS_ROUTES
value: "{{TS_ROUTES}}"

View File

@ -22,9 +22,9 @@ spec:
value: "{{TS_KUBE_SECRET}}"
- name: TS_USERSPACE
value: "true"
- name: TS_AUTH_KEY
- name: TS_AUTHKEY
valueFrom:
secretKeyRef:
name: tailscale-auth
key: TS_AUTH_KEY
key: TS_AUTHKEY
optional: true