Hacker News Reader

Comment by barnabask | Hacker News Reader

Going by blog posts, 1.17 was released 2019-12-09, 1.18 was released 2020-03-25, 1.19 was released 2020-08-26, and 1.20 was released 2020-12-08 (today). Great cadence.

AWS EKS seems to support major versions six or seven months later. Support for 1.17 was announced 2020-07-13, 1.18 was announced 2020-10-13. I'm guessing we can plan for 1.20 support on EKS around June of 2021. No judgement, just an observation.

View on HN

That cadence is also exhausting to follow, I wish they made an LTS sort of release so people can catch a break.

I feel you. Keeping up with kubernetes feels like a ratrace.

This is one of Kubernetes' biggest downfalls. On a small team, time is king. You likely don't have a team dedicated to keeping up with Kube releases, troubleshooting issues, etc.

When you build something, you need it to work until _you_ decide to futz with it again.

This is our pain.. the main reason why we are seeking other alternatives to K8S.

Hashicorp’s Nomad? Just hit 1.0.

That's something I'd be curious about. How do you feel a later migration from Nomad to k8s would go?

Straightforward imo (go containers first if this is your eventual intent), with the effort involved dependent on what your service mesh, networking, and storage situation and requirements looks like. More complexity is of course going to make such an effort more work.

Openshift does have LTS. The recently released version 4.6 is planned as one.

supported are 3 minor releases with (1.18) 9months and newer minors 1year updates. you should always upgrade to one version behind the last major in self managed scenarios. i.e. my company is on 1.18 and goes to 1.19 now. basically if something breaks it's most often not the end of the world, especially not if you do backups with velero.

Reply on news.ycombinator.com