4 ms·

1.10.4 was released only earlier this year and is no longer supported. C’mon, Kubernetes.

by deboflo 8y ago

colek42 8y ago
The release cadence is public. If you run upstream be ready to do frequent updates. If you are a cloud provider you should also be ready to do frequent upgrades.
bonsai80 8y ago
How can I know if a version is no longer supported? I found their docs talking about the four previous versions, but that seems to just be about the documentation and I can't find a statement about the software itself. Does the Kubernetes project do anything like Ubuntu or Node.js with the LTS concept, or is it a situation where you need to be running a version within the last x releases?
- gtirloni 8y ago
  No, there is no concept of LTS in upstream Kubernetes yet. That's currently a job for the "distributions" (OpenShift, Canonical, GKE, Azure, etc). Regarding supported versions, it seems the project still aims to support 3 versions at a time. You can read more about it here: https://github.com/kubernetes/community/blob/master/contributors/design-proposals/release/versioning.md#supported-releases-and-component-skew https://github.com/kubernetes/community/blob/master/contribu... You often find some confusing statements about supported versions because sometimes they're talking about version skew between different components. More about that here: https://github.com/kubernetes/website/issues/7103 https://github.com/kubernetes/website/issues/7103
  - bonsai80 8y ago
    Thanks, that's just what I was looking for!
sieabahlpark 8y ago
They're busy at re:Invent
- sbkg0002 8y ago
  Busy, but not with eks. No word on containers during the keynotes.
falcolas 8y ago
I tend to agree with you. Move Fast and Break Things has broken our industry in many fundamental ways. Just moving from 1.10 to 1.13 will result in broken integrations due to changed/deprecated APIs, no matter that it's a minor version change.

4 ms·

1.10.4 was released only earlier this year and is no longer supported. C’mon, Kubernetes.

by deboflo 8y ago

1.10.4 was released only earlier this year and is no longer supported. C’mon, Kubernetes.

colek42 8y ago
The release cadence is public. If you run upstream be ready to do frequent updates. If you are a cloud provider you should also be ready to do frequent upgrades.
bonsai80 8y ago
How can I know if a version is no longer supported? I found their docs talking about the four previous versions, but that seems to just be about the documentation and I can't find a statement about the software itself. Does the Kubernetes project do anything like Ubuntu or Node.js with the LTS concept, or is it a situation where you need to be running a version within the last x releases?
- gtirloni 8y ago
  No, there is no concept of LTS in upstream Kubernetes yet. That's currently a job for the "distributions" (OpenShift, Canonical, GKE, Azure, etc). Regarding supported versions, it seems the project still aims to support 3 versions at a time. You can read more about it here: https://github.com/kubernetes/community/blob/master/contributors/design-proposals/release/versioning.md#supported-releases-and-component-skew https://github.com/kubernetes/community/blob/master/contribu... You often find some confusing statements about supported versions because sometimes they're talking about version skew between different components. More about that here: https://github.com/kubernetes/website/issues/7103 https://github.com/kubernetes/website/issues/7103
  - bonsai80 8y ago
    Thanks, that's just what I was looking for!
sieabahlpark 8y ago
They're busy at re:Invent
- sbkg0002 8y ago
  Busy, but not with eks. No word on containers during the keynotes.
falcolas 8y ago
I tend to agree with you. Move Fast and Break Things has broken our industry in many fundamental ways. Just moving from 1.10 to 1.13 will result in broken integrations due to changed/deprecated APIs, no matter that it's a minor version change.