Kubernetes 1.8.3 dropped this week and my feeds have been wall to wall with it. Which is funny, because it is a patch release. No headline feature, just a stack of bug fixes and the usual scheduler and kubelet tidy-ups. The internet got excited anyway.
I am genuinely pleased about that. The interesting releases are the ones where you read the notes with one eye closed, waiting to find out which of your assumptions just stopped being true. A boring point release is the opposite: things you already rely on now break slightly less often. That is the whole job.
We are still on 1.7 at work and in no rush to move. I will let 1.8 settle through a couple more patches before I think about it, because every time I have chased the latest minor in a hurry I have regretted it within a fortnight. The cluster does not care that a version is new. It cares that the bits I depend on keep doing what they did yesterday.
So, well done to everyone who shipped a release nobody will remember. That is praise, honestly.