Live data from Hacker News

The Cult of Kubernetes

christine.website

11–20 of 338 posts

Re: The Cult of Kubernetes

#11
post #4

I am one of these guys who is using K8S at home. The reason is a unified platform for work and home environment.

How do you expose your services via an ingress when it needs to be behind a nat (via your home router/gateway)? Thanks!

One possibility (especially for "home Kubernetes" case) is not exposing the services to the outside world at all and using ZeroTier to access them https://www.zerotier.com/ It's L2 mesh VPN, and I believe you can even use MetalLB with it with some minor trickery. You can, of course, set up WireGuard or OpenVPN for yourself, too, but from my experience zt is the simplest for accessing the boxes behind NAT as you don't even need to set up any servers with real IPs.

Re: The Cult of Kubernetes

#12
I think devs often make bad decision makers because in some sense tech is often an addiction rather than a pragmatic choice.

The cycle of picking a tech, jumping ship to it, religiously evangelising it, riding the wave and then jumping ship to the next related tech is typical in my opinion.

I try hard to correct for this bias but sometimes struggle with exactly the same thing. There's just something about wanting to have a uniform "world-view" with fewer explanatory variables that never stops being motivating.

Re: The Cult of Kubernetes

#13
post #5
post #3

Earlier quoted context omitted.

What's the cheapest you can run a k8s cluster in the cloud? I've been looking to spin one up in AWS, but it looks remarkably expensive for running personal projects.

I run a very small GKE cluster with two 1vCPU preemptible nodes. Costs me a few bucks per month.

I was thinking of doing the same thing. How much in average do you pay per month?

Re: The Cult of Kubernetes

#14
post #12

I think devs often make bad decision makers because in some sense tech is often an addiction rather than a pragmatic choice. The cycle of picking a tech, jumping ship to it, religiously evangelising it, riding the wave and then jumping ship to the next related tech is typical in my opinion. I try hard to correct for this bias but sometimes struggle with exactly the same thing. There's just something about wanting to…

It helps working for big corps.

The job might not be as interessing as riding every tech wave, but on the plus side there are plenty of tech waves that you save yourself from riding on.

Plus one gets to rescue projects that ended up betting on the wrong waves, getting back to boring old tech.

Re: The Cult of Kubernetes

#15
post #12

I think devs often make bad decision makers because in some sense tech is often an addiction rather than a pragmatic choice. The cycle of picking a tech, jumping ship to it, religiously evangelising it, riding the wave and then jumping ship to the next related tech is typical in my opinion. I try hard to correct for this bias but sometimes struggle with exactly the same thing. There's just something about wanting to…

You could say that to pretty much any technical abstraction though.

Re: The Cult of Kubernetes

#16
post #12

I think devs often make bad decision makers because in some sense tech is often an addiction rather than a pragmatic choice. The cycle of picking a tech, jumping ship to it, religiously evangelising it, riding the wave and then jumping ship to the next related tech is typical in my opinion. I try hard to correct for this bias but sometimes struggle with exactly the same thing. There's just something about wanting to…

You could say that to pretty much any technical abstraction though.

I entirely agree... in fact it applies to me more with maths than it does with tech.

Re: The Cult of Kubernetes

#18
post #12

I think devs often make bad decision makers because in some sense tech is often an addiction rather than a pragmatic choice. The cycle of picking a tech, jumping ship to it, religiously evangelising it, riding the wave and then jumping ship to the next related tech is typical in my opinion. I try hard to correct for this bias but sometimes struggle with exactly the same thing. There's just something about wanting to…

Additional factors I'd want to add:

Confirmation bias (where you've spent some time on k8s or whatever, and now you just want to cash in on your time loss, objective criteria be damned)

Generational churn (where you find yourself in a field where everything has been said and done, and you just need a new buzzword on your resume to start over; this goes hand-in-hand with corporate IT longing for fresh and cheap staff and their stack in need to look sexy)

Big media (where extremely large infrastructure runs on k8s or whatever, and gets disproportional airtime, because cloud providers want to sell you lots of pods, and people not checking whether the proposed arch is a good fit)

Re: The Cult of Kubernetes

#19
post #4

I am one of these guys who is using K8S at home. The reason is a unified platform for work and home environment.

How do you expose your services via an ingress when it needs to be behind a nat (via your home router/gateway)? Thanks!

Hi, my shameless plug (I am the creator of webhookrelay): https://webhookrelay.com/v1/guide/ingress-controller, using it both for services that are running in GKE and on minikube locally. It's cheaper than allocating a LB IP for backing services that don't get much traffic like Grafana and similar things.

Re: The Cult of Kubernetes

#20
post #3

I am one of these guys who is using K8S at home. The reason is a unified platform for work and home environment.

What's the cheapest you can run a k8s cluster in the cloud? I've been looking to spin one up in AWS, but it looks remarkably expensive for running personal projects.

If you just/first want to practice actual, multi-node k8s on your local Mac (or Windows), I've just completed this: https://github.com/youurayy/hyperctl
Post reply on HN