Exposing k3s Pods to the Tailnet
2024-01-16Background
What instigated this was trying to use csi-driver-smb to connect to a SMB share that’s exposed on my Tailnet. If I ever get that working, that’ll be a separate post altogether.
This is a short post to simply document a snippet of progress.
Desired State
What I really wanted was to have my SMB share, which is on my Tailnet, be mounted in using csi-driver-smb to expose its contents to the cluster. This would theoretically release the host node from needing to mount a SMB share directly, during bootup, and keep everything contained to the cluster. The end-goal was portability.
This has yet to happen (successfully).
Minor Details
Essentially, the Tailscale docs on adding Tailscale to a k8s cluster and their k8s operator are spot-on. I ran into no memorable complications.
What’s Next
I’ve put the overarching project (k3s mounting an SMB share over the tailnet) on an indefinite hiatus. The current workaround is to spin up relatively small VMs in my proxmox cluster, and have the VM guests execute the SMB mounts themselves.
Not the best solution, but it works for the very few instances I need this.
If the need grows, over time, I’ll have to revisit this.