Live data from Hacker News

Ask HN: Is it still worth learning Kubernetes in 2022?

news.ycombinator.com

51–57 of 57 posts

Re: Ask HN: Is it still worth learning Kubernetes in 2022?

#51

Heya, there are free courses on Coursera you could take a look at - just to get a taste. Since you mentioned you do ML and work with AWS, perhaps check out this free course on building containerised applications in AWS: https://www.coursera.org/learn/containerized-apps-on-aws It’s only 12 hours, so a minimal time investment. And from there you can then decide your next step. Good luck! And happy new year ^_^

Any other recommendations outside of aws?

Re: Ask HN: Is it still worth learning Kubernetes in 2022?

#52

For horizontal and automatic scaling, I don't see many other viable alternatives for managing networking, load balancing, configuration and scheduling. Most server software these days have Kubernetes and helm charts available, since the industry giants focus on it, which means it's here to stay. It might be worth getting a certification in Kubernetes orchestration management instead, like Rancher or Nomad (with Vault…

I was just going to mention Nomad, Consul et al. They’re maturing well and Nomad is light on resources.

Re: Ask HN: Is it still worth learning Kubernetes in 2022?

#54

No. It adds nothing but unneeded complexity to the stack. Learn how to package your software and use the package manager. You can combine that, if you must, with any kind of config manager like Ansible or something else. So many companies are doing what's "trendy and shiny", and it can almost look like it is becoming a de-facto standard, but they will eventually realize the mistake.

Learning ansible in 2022 would be what's a waste of effort as every company that I know is phasing it out in favour of immutable infrastructure via OCI images. It's been 7 years. Kubernetes isn't trendy or shiny. The teams using it use it because of legitimate reasons.

I'm not sure how you can replace your infrastructure with an OCI image, provided that OCI image means a container image?

I don't think Ansible is a waste of effort. For example, we have OpenStack images that we spawn, but use Ansible to have repeatable builds of those images. Additionally, you can learn enough Ansible in a weekend to be dangerous. IMO the payoff is there, it's a very simple yet effective framework, depending on your usecases.

Re: Ask HN: Is it still worth learning Kubernetes in 2022?

#56
post #50

Earlier quoted context omitted.

I do wonder sometimes if (you're willing to stick to Java then) you could use OSGI and get a lot of the same benefits. But I never went that far into OSGI to really know, and I like SQLAlchemy too much these days!

OSGI is bloated and pretentious, just use the classloader, it takes 300 lines of code and you have the best container in the world, see my Archive class: https://github.com/tinspin/rupy/blob/master/src/se/rupy/http... What does SQLAlchemy have to do with containers?

I must have been tired. I meant I don't want to only use Java, and thus I can't use OSGI (or the classloader - I'm sure you're right); Docker and k8s are definitely good for allowing you to use whatever tools you like.

Re: Ask HN: Is it still worth learning Kubernetes in 2022?

#57

No. It adds nothing but unneeded complexity to the stack. Learn how to package your software and use the package manager. You can combine that, if you must, with any kind of config manager like Ansible or something else. So many companies are doing what's "trendy and shiny", and it can almost look like it is becoming a de-facto standard, but they will eventually realize the mistake.

Learning ansible in 2022 would be what's a waste of effort as every company that I know is phasing it out in favour of immutable infrastructure via OCI images. It's been 7 years. Kubernetes isn't trendy or shiny. The teams using it use it because of legitimate reasons.

Ansible is not a waste of time. It's a tool for a certain set of tasks.

I learned Ansible in 2021 after mainly having used Kubernetes, Helm and Terraform at work.

I did that because I needed to deploy self-hosted Kubernetes nodes, virtual machines and VPNs; while there are Terraform providers (drivers) for open-source hypervisors, you still need to get your OS from vanilla to installed-and-configured. Ansible does that.

And yes, you could build install images and deploy them directly on your hardware. But with certain non-cloud datacenters, the pick-your-image option is sometimes limited. Being able to pick some preferred vanilla image and run the same commands to get the same node up and running is just so easy to experiment with, and it works even before your image registry server is up and running.

Post reply on HN