3 ms·
As a frame of reference, if one were currently on a 12 year old Kubernetes release you'd be running (charitably) 1.0.0 because this is the earliest snap I could
by mdaniel 2y ago
As a frame of reference, if one were currently on a 12 year old Kubernetes release you'd be running (charitably) 1.0.0 because this is the earliest snap I could find of kubernetes.io and it doesn't even have a version number https://web.archive.org/web/20141114180626/http://kubernetes.io:80/ https://web.archive.org/web/20141114180626/http://kubernetes... [1]
So, I hear them about "but I wanna run 1.32 on my PBX for-evvvvvah" but I don't think that choice is going to do what they expect. Hell, I'd gravely wonder if containerd would survive a 12 year old release cycle
1: chasing the API docs, one can see the 12 year old control plane managed three resource types: Pods, ReplicationControllers, and Services https://web.archive.org/web/20141013032652/http://cdn.rawgit.com/GoogleCloudPlatform/kubernetes/31a0daae3627c91bc96e1f02a6344cd76e294791/api/kubernetes.html https://web.archive.org/web/20141013032652/http://cdn.rawgit...
- Palomides 2y agonow that it's 12 years later, maybe kubernetes is more feature complete, stable, and possible to maintain at one version
- deleted 2y ago[deleted]