4 ms·

They need some sort of LTS versioning. Keeping up with their breakneck development pace is a job all its own.

by ascendantlogic 9y ago

manojlds 9y ago
Kops has not released a 1.9 version yet. Even k8s projects can't keep up.
- AlexB138 9y ago
  Kops generally stays one release behind. 1.9 is being end to end tested in the last week. I wouldn't use that as an example of not keeping up, it's the established cycle for the project.
  - justinsb 9y ago
    kops 1.9 is very close to ready now, but this is a longer lag than normal. We've historically released kops 1.x when we consider that k8s 1.x is stable, including all the networking providers and ecosystem components. That's typically about a month after release. User feedback has been that that we want to keep that, but that we should also offer an alpha/beta of 1.10 much sooner, so that users that want to try out 1.10 today can do so (and so we get feedback earlier). So watch for kops 1.10 alpha very soon, and 1.11 alpha much earlier in the 1.11 cycle.
    - iooi 9y ago
      For those that aren't aware, justinsb is the author of kops. Looking forward to the 1.9 release.
      - justinsb 9y ago
        Ah - sorry, probably should have disclaimered that! I did write the original kops code, but now there's a pretty active set of contributors working on kops (and contributions are always welcome and appreciated!)
raesene9 9y ago
Yep at the moment (AFAIK) support is essentially for 9 months from release (current release + 2 previous) so without an LTS process, everyone has to upgrade at least that often to keep getting security patches...
kokey 9y ago
I think LTS type of implementations are down to container services providers and things like OpenShift.
- oblio 9y ago
  The Linux kernel is part of distributions yet it still has LTSes. It seems a valid complaint.
twakefield 9y ago
We published a post about this a couple months ago which might interest you[0]. Here's the HN discussion in case you missed it[1]. [0] https://gravitational.com/blog/kubernetes-release-cycle/ https://gravitational.com/blog/kubernetes-release-cycle/ [1] https://news.ycombinator.com/item?id=16285192 https://news.ycombinator.com/item?id=16285192
- ascendantlogic 9y ago
  "TL;DR - Unabated 1.xx major “minor” releases of “vanilla” upstream Kubernetes every three months could continue forever. You have to keep up, while also paying close attention to Kubernetes API object versioning. This relentless pace is the key ingredient in Kubernetes’ domination of the distributed infrastructure world." Did you just tell me to go fuck myself? :D
bproven 9y ago
Agreed. This would also reduce mid/large enterprise worries regarding adoption (or investigating the tech for possible adoption). Being on the upgrade train several times a year is too probably much for them...

They need some sort of LTS versioning. Keeping up with their breakneck development pace is a job all its own.

manojlds 9y ago

Kops has not released a 1.9 version yet. Even k8s projects can't keep up.

AlexB138 9y ago
Kops generally stays one release behind. 1.9 is being end to end tested in the last week. I wouldn't use that as an example of not keeping up, it's the established cycle for the project.
- justinsb 9y ago
  kops 1.9 is very close to ready now, but this is a longer lag than normal. We've historically released kops 1.x when we consider that k8s 1.x is stable, including all the networking providers and ecosystem components. That's typically about a month after release. User feedback has been that that we want to keep that, but that we should also offer an alpha/beta of 1.10 much sooner, so that users that want to try out 1.10 today can do so (and so we get feedback earlier). So watch for kops 1.10 alpha very soon, and 1.11 alpha much earlier in the 1.11 cycle.
  - iooi 9y ago
    For those that aren't aware, justinsb is the author of kops. Looking forward to the 1.9 release.
    - justinsb 9y ago
      Ah - sorry, probably should have disclaimered that! I did write the original kops code, but now there's a pretty active set of contributors working on kops (and contributions are always welcome and appreciated!)

raesene9 9y ago

Yep at the moment (AFAIK) support is essentially for 9 months from release (current release + 2 previous) so without an LTS process, everyone has to upgrade at least that often to keep getting security patches...

kokey 9y ago

I think LTS type of implementations are down to container services providers and things like OpenShift.

oblio 9y ago
The Linux kernel is part of distributions yet it still has LTSes. It seems a valid complaint.

twakefield 9y ago

We published a post about this a couple months ago which might interest you[0]. Here's the HN discussion in case you missed it[1]. [0] https://gravitational.com/blog/kubernetes-release-cycle/ https://gravitational.com/blog/kubernetes-release-cycle/ [1] https://news.ycombinator.com/item?id=16285192 https://news.ycombinator.com/item?id=16285192

ascendantlogic 9y ago
"TL;DR - Unabated 1.xx major “minor” releases of “vanilla” upstream Kubernetes every three months could continue forever. You have to keep up, while also paying close attention to Kubernetes API object versioning. This relentless pace is the key ingredient in Kubernetes’ domination of the distributed infrastructure world." Did you just tell me to go fuck myself? :D

bproven 9y ago

Agreed. This would also reduce mid/large enterprise worries regarding adoption (or investigating the tech for possible adoption). Being on the upgrade train several times a year is too probably much for them...