Live data from Hacker News

The Cult of Kubernetes

christine.website

101–110 of 338 posts

Re: The Cult of Kubernetes

#101

Kubernetes is our one shot at having the universal vendor-neutral cluster interface. The fact that it's time consuming to do simple things directly against it doesn't surprise me in the same way I'm not surprised that writing todo app directly against POSIX abstraction would be time consuming. It's a great way to learn how these interfaces work though.

[deleted]

Re: The Cult of Kubernetes

#102
post #82
post #65

Earlier quoted context omitted.

You're not eliminating "dev ops", you're doing it right.

Eliminating dev ops is doing it right! The whole entire point of devops, as it was originally formed, was that making developers bear the load of operations would encourage them to simplify and automate it.

I should have added scare quotes around "eliminating", too, it seems :-)

Re: The Cult of Kubernetes

#103
post #52

Earlier quoted context omitted.

I worked for someone who had mindset that whatever technology developers wanted was always good and ops should just shut up and put up with it because devs are the ones that make the money for the business. Very infuriating mindset to deal with.

And I've worked at companies where the devs where expected to know their place and not question ops, because ops was seen as the serious adults in the room keeping things running and devs where seen as easily distracted children chasing after the shiniest thing that most recently caught their attention. Made perfect sense when I was on the ops side and was super annoying when I was on the dev side :) Imagine if peopl…

Having worked in both DevOps (or Ops as we called it in 2002), there really was a belief that the developers were stupid, and they'd burn the whole place down if we gave them any leeway. As a developer, I've seen DevOps as a frustrating gate at times. The only things I think can fix this divide are communication and built trust. (and probably less assumed malice)

Re: The Cult of Kubernetes

#104
post #99
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…

Part of the problem is the hiring process (plus attitudes seen on here). Your resume needs to have lots of fashionable buzzwords rather than pragmatic good enough / keep it simple choices. You must keep on learning (lots of things rather than mastering any one thing). I can write a really nice site in standard Django with some JQuery, and it will take me half the time that adding React to it will. But adding React wi…

The real trick is to make your site load so fast people swear it's magic. I use a combination of serving things from ram and https://instant.page to do this with a fairly boring plain old HTML rendering on the server app. I even have a Progressive Web App out of it too.

Re: The Cult of Kubernetes

#105

Earlier quoted context omitted.

Consider just running Minikube on your laptop. It’s pretty realistic and won’t cost you a penny. Except maybe in electricity, it seems to consume an enormous wattage just to exist...

minikube --vm-driver=none consumes a lot less resources, and k3s even fewer.

K3s is fantastic. Lately I've been using K3d (which is the same thing, just in a docker container - much like Kind) It's super easy to spin up a cluster, and spin it back down with nothing really to clean up.

Re: The Cult of Kubernetes

#106
post #53

Author of the post here, feel free to ask me anything!

Thank you for posting your experience. I am starting on the same path. I am at the point where I got the deployment working and a pod setup. Now I need to be able to access my service from the Internet using a DNS name and SSL certs. Before reading your post I didn't realize how many supporting characters would be needed to do this. It feels daunting and am grateful you posted your scripts and configurations. I'm run…

AWS K8 either requires managing the master(s)/etcd yourself or paying amazon to do it via EKS. Amazon charges $150/cluster/month for the masters/etcd in EKS. As I understand it, Google and Digital Ocean charge $0/month for the master(s)/etcd.

So if $150/cluster/month is an amount that matters to you then you shouldn't use EKS.

Re: The Cult of Kubernetes

#107
post #28

Earlier quoted context omitted.

I'm using K8S (with rancher's k3s) at home too ! My main reason is portability. When I need to unplug one of the Raspberries or move all services to somewhere else, I only need to change the storage layer.

So you're running bare metal k8s at home? What do you use for storage? That's my biggest question in how to move frok minikube at home to a true cluster.

Raid 1, 4tb, NAS with NFS :)

Re: The Cult of Kubernetes

#108
post #31
post #27

Earlier quoted context omitted.

You mean, Kubernetes is the COBOL of 2050?

I mean that Kubernetes is the NoSQL, CoffeScript, BigData, Grails, SOAP... of 2019. It is a bit unfair for Cobol, given that its latest revision is from 2014, and while verbose as it might be, it supports most of the nice features of any modern multi-paradigm language.

I think this is a bit unfair to SOAP.

SOAP was\is a pretty stable technology that did exactly what it promised to do, without too many releases or breaking changes for about 10 years.

Even today it has a good utility for the situations it is designed for...

RPC over a well known standard format, for tightly coupled endpoints, that require metadata, enforced schema, security, and perhaps transactions.

big problem for SOAP is it was the default for web services for a long time, when in reality a big shift happened in about 2008 where webservices were most likely NOT going to fit into those constraints. just my 2 cent

Re: The Cult of Kubernetes

#109
post #78
post #62

Calling it a cult after growing up in one is a bit insulting. But, yes, I don't run much on my personal K8s clusters. But, I've lost count of how many problems Kubernetes has solved for folks I've worked with. It might not solve the simplicity use cases but, that's not the intended design of the tool to begin with.

- The group displays excessively zealous and unquestioning commitment to its leader - Questioning, doubt and dissent are discouraged or even punished - Mind-altering practices are used in excess to suppress doubts (corporate-speak counts) - The group is elitist - The group has a polarized us-versus-them mentality, which may cause conflict with the wider society - The leader is not accountable to any authorities - The…

[deleted]

Re: The Cult of Kubernetes

#110
post #83

Earlier quoted context omitted.

I think jumping on new tech and marketing yourself is a good decision for a developer as its a good way to increase their compensation and market value. If you're a developer stuck maintaining a Java spring app at some unknown company the best way to make a shift is to pick up Go or something and move to a startup. Else your career will stagnate. The best way to get promoted at many companies is to write a framework.…

Is this really true? There are plenty of job openings for people who are good at maintaining Java Spring apps!

They also pay a fraction of what the jobs "hip" companies pay, and often come along with developers Being treated as second-class citizens.
Post reply on HN