47ace13ac8
Use the correct KUBE_SECRET value |
||
---|---|---|
.. | ||
Dockerfile | ||
Makefile | ||
proxy.yaml | ||
README.md | ||
role.yaml | ||
rolebinding.yaml | ||
run.sh | ||
sa.yaml | ||
sidecar.yaml | ||
userspace-sidecar.yaml |
Overview
There are quite a few ways of running Tailscale inside a Kubernetes Cluster, some of the common ones are covered in this doc.
Instructions
Setup
-
(Optional) Create the following secret which will automate login.
You will need to get an auth key from Tailscale Admin Console.
If you don't provide the key, you can still authenticate using the url in the logs.apiVersion: v1 kind: Secret metadata: name: tailscale-auth stringData: AUTH_KEY: tskey-...
-
Build and push the container
export IMAGE_TAG=tailscale-k8s:latest make push
-
Tailscale (v1.16+) supports storing state inside a Kubernetes Secret.
Configure RBAC to allow the Tailscale pod to read/write the
tailscale
secret.export SA_NAME=tailscale export KUBE_SECRET=tailscale-auth make rbac
Sample Sidecar
Running as a sidecar allows you to directly expose a Kubernetes pod over Tailscale. This is particularly useful if you do not wish to expose a service on the public internet. This method allows bi-directional connectivty between the pod and other devices on the Tailnet. You can use ACLs to control traffic flow.
-
Create and login to the sample nginx pod with a Tailscale sidecar
make sidecar # If not using an auth key, authenticate by grabbing the Login URL here: kubectl logs nginx ts-sidecar
-
Check if you can to connect to nginx over Tailscale:
curl http://nginx
Or, if you have MagicDNS disabled:
curl "http://$(tailscale ip -4 nginx)"
Userspace Sidecar
You can also run the sidecar in userspace mode. The obvious benefit is reducing the amount of permissions Tailscale needs to run, the downside is that for outbound connectivity from the pod to the Tailnet you would need to use either the SOCKS proxy or HTTP proxy.
-
Create and login to the sample nginx pod with a Tailscale sidecar
make userspace-sidecar # If not using an auth key, authenticate by grabbing the Login URL here: kubectl logs nginx ts-sidecar
-
Check if you can to connect to nginx over Tailscale:
curl http://nginx
Or, if you have MagicDNS disabled:
curl "http://$(tailscale ip -4 nginx)"
Sample Proxy
Running a Tailscale proxy allows you to provide inbound connectivity to a Kubernetes Service.
-
Provide the
ClusterIP
of the service you want to reach by either:Creating a new deployment
kubectl create deployment nginx --image nginx kubectl expose deployment nginx --port 80 export DEST_IP="$(kubectl get svc nginx -o=jsonpath='{.spec.clusterIP}')"
Using an existing service
export DEST_IP="$(kubectl get svc <SVC_NAME> -o=jsonpath='{.spec.clusterIP}')"
-
Deploy the proxy pod
make proxy # If not using an auth key, authenticate by grabbing the Login URL here: kubectl logs proxy
-
Check if you can to connect to nginx over Tailscale:
curl http://proxy
Or, if you have MagicDNS disabled:
curl "http://$(tailscale ip -4 proxy)"