Kubernetes 1.13 released(kubernetes.io)
kubernetes.io
Kubernetes 1.13 released
https://kubernetes.io/blog/2018/12/03/kubernetes-1-13-release-announcement/
16 comments
Whelp. That puts Amazon's EKS on a non-supported version (1.10.4) of Kubernetes then. :/
C'mon, Amazon.
C'mon, Amazon.
1.10.4 was released only earlier this year and is no longer supported. C’mon, Kubernetes.
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.
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.
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?
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/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
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/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
Thanks, that's just what I was looking for!
They're busy at re:Invent
Busy, but not with eks. No word on containers during the keynotes.
make sure you're not affected
https://www.redhat.com/en/blog/understanding-critical-kubern...
What does that even mean to support it? It's not like you can't ask questions the general community to get answers. You also don't have a support contract with it since it's open source software. And if they did release a patch for it, you might as well upgrade anyways since there are tons of new fixes.
This is defined here: https://github.com/kubernetes/community/blob/b3349d5b1354df8...
Specifically, a supported release is one which will receive patch updates (e.g. for security flaws or other issues).
If you do not use a "supported version", you'll have to scramble to update or backport patches yourself if you're hit by a serious issue that is fixed upstream.
Specifically, a supported release is one which will receive patch updates (e.g. for security flaws or other issues).
If you do not use a "supported version", you'll have to scramble to update or backport patches yourself if you're hit by a serious issue that is fixed upstream.
All versions of kubernetes >= 1.10 and < 1.13 are affected I believe.
Kops 1.11 is still in beta
Yes, we're waiting till 1.11.6 lands - some important fixes for clouds in there. We've debated releasing at the same time as Kubernetes, but the feedback we've got is that users prefer that a kops release is ready to run, but we also need to do a better job of releasing alphas & betas earlier.
Obviously the current delay is not great - I'd much prefer for us to be on 1.12 (which actually has fixed the main issue already). I'm hoping we can catch up once we're (finally) done with the etcd3 migration.
Obviously the current delay is not great - I'd much prefer for us to be on 1.12 (which actually has fixed the main issue already). I'm hoping we can catch up once we're (finally) done with the etcd3 migration.
- It is now possible to use named ports in the kubectl port-forward command (#69477, @m1kola)
- kubectl: support multiple arguments for cordon/uncordon and drain (#68655, @goodluckbot)
The new kubectl plugin method reaching beta is exciting too