The full-time job of keeping up with Kubernetes

Re:The full-time job of keeping up with Kubernetes by maxxxxx on Thursday February 01, 2018 @04:45PM (#16286224)

I think this is a symptom of the "release often" philosophy. With yearly or longer releases you could actually keep up and read the release notes. With stuff being released several times a year it's too much work to keep up unless you are deeply into it at the moment.

I notice the same with my Android apps. I used to read release notes of new versions but now I have it on auto update and am sometimes surprised that an app I have been using all the time has completely changed and I don't know how to use it anymore.

[ Parent | on HN ]

Re:The full-time job of keeping up with Kubernetes by praseodym on Thursday February 01, 2018 @05:09PM (#16286409)

No, it is the symptom of a high velocity project. If Kubernetes were to have yearly releases, the list of changes would be four times as long and upgrade path would be a major leap instead of four minor steps.

[ Parent | on HN ]

Re:The full-time job of keeping up with Kubernetes by maxxxxx on Thursday February 01, 2018 @06:25PM (#16286923)

I think a major leap is much easier to handle and to plan for.

[ Parent | on HN ]

Re:The full-time job of keeping up with Kubernetes by shaftoe on Thursday February 01, 2018 @08:18PM (#16287565)

I completely disagree. The complexity and risk of a change goes up with the square of the size of the change. Having moved from upgrading when forced to (almost) continuous upgrading, the number of moving parts in any given change is small and the frequency means we become skilled at rolling out changes safely.

[ Parent | on HN ]

Re:The full-time job of keeping up with Kubernetes by gatmne on Friday February 02, 2018 @01:17AM (#16288774)

That's fine and dandy if you can afford to put up the resources to keep your deployment up to date. For more constrained others, an LTS release can be the deference between using the project vs not.

[ Parent | on HN ]