Tailscale Kubernetes Operator

#1

Post by l2dy » Fri, Sep 22, 2023, 12:39 PM UTC

Tailscale Kubernetes Operator
tailscale.com

Re: Tailscale Kubernetes Operator

#2

Post by thelastparadise » Fri, Sep 22, 2023, 1:01 PM UTC

It's a neat idea but I wouldn't put this in my k8s cluster.

Keep it simple st*pid!

Re: Tailscale Kubernetes Operator

#3

Post by leetrout » Fri, Sep 22, 2023, 1:02 PM UTC

thelastparadise wrote: post #2

It's a neat idea but I wouldn't put this in my k8s cluster. Keep it simple st*pid!

You can use, instead:

Keep it simple, smarty

Re: Tailscale Kubernetes Operator

#4

Post by gmemstr » Fri, Sep 22, 2023, 1:03 PM UTC

Maybe not wise to post here yet as the docs mark this as a private alpha.

Re: Tailscale Kubernetes Operator

#5

Post by tecleandor » Fri, Sep 22, 2023, 1:04 PM UTC

Nice! I think I'll try to implement this in my TrueNAS this weekend, as it makes way way easier to access all the services I deploy there.

TrueCharts charts have Tailscale support, but not all my charts are from there, and also I'm kind of avoiding them.

Also, it's nice if you deploy something without a chart.

Re: Tailscale Kubernetes Operator

#6

Post by [deleted] » Fri, Sep 22, 2023, 1:09 PM UTC

leetrout wrote: post #3

thelastparadise wrote: post #2

It's a neat idea but I wouldn't put this in my k8s cluster. Keep it simple st*pid!

You can use, instead: Keep it simple, smarty

[deleted]

Re: Tailscale Kubernetes Operator

#7

Post by ses1984 » Fri, Sep 22, 2023, 1:14 PM UTC

leetrout wrote: post #3

thelastparadise wrote: post #2

It's a neat idea but I wouldn't put this in my k8s cluster. Keep it simple st*pid!

You can use, instead: Keep it simple, smarty

Keep it super simple.

Re: Tailscale Kubernetes Operator

#8

Post by birdyrooster » Fri, Sep 22, 2023, 1:18 PM UTC

leetrout wrote: post #3

thelastparadise wrote: post #2

It's a neat idea but I wouldn't put this in my k8s cluster. Keep it simple st*pid!

You can use, instead: Keep it simple, smarty

[flagged]

Re: Tailscale Kubernetes Operator

#9

Post by yebyen » Fri, Sep 22, 2023, 1:18 PM UTC

gmemstr wrote: post #4

Maybe not wise to post here yet as the docs mark this as a private alpha.

Maybe so, as what we're doing in absence of proper docs is rightly classified as something worse than alpha. The best docs they had so far up to this point:

https://tailscale.com/kb/1185/kubernetes/

These are great, for someone who knows Kubernetes. You should understand that creating the tailscale subnet router as a pod directly means the connection is not resilient. It's also key to understand that tailscale will break if you have more than one instance of subnet router at a time, so substituting Deployment in place of where these docs use Pod is not a really good choice without some fine tuning because of the risk that a rolling update creates another copy of the pod before the old one has shut down.

Maybe stateful set, if there was a way to permanently imply that statefulset can only have one replica. I appreciate the link anyway. I figured all this out on my own, and I'm using tailscale productively with Kubernetes based on the old docs, with my open source project. Tailscale has a great and generous free software tier for supporting OSS maintainers. :tada:

Re: Tailscale Kubernetes Operator

#10

Post by HappyCathode » Fri, Sep 22, 2023, 1:21 PM UTC

That's really neat. Cloudflare tunnel for external customer egress, and Tailscale for internal tool egress. No more costly cloud specific load balancers !