Maintaining the Kubernetes Life Cycle by The New Stack Makers published on 2017-08-25T00:50:11Z Kubernetes now faces an evolutionary hurdle that only Docker before it has faced so soon in its life cycle: the problem of multiple concurrent versions. Version 1.7 is upon us today, even though other versions are still in active use. At the rate Kubernetes is evolving now, over a dozen viable versions could be deployed over the standard life cycle of organizations’ IT projects — some three to four years’ time. “We try to make every new Kubernetes release as stable as possible,” said Caleb Miles, who leads the Kubernetes Project Management SIG. “We have a long code freeze and stabilization period to shake out any of the rough edges before a new version of Kubernetes lands.” Learn more about how the Project Management SIG maintains consistency and concurrency without introducing obsolescence, in this special edition of The New Stack Makers podcast. Genre Technology Comment by The New Stack Makers Determining the CNCF's responsibility for providing the bigger picture of the Kubernetes ecosystem. 2017-09-01T22:45:28Z Comment by The New Stack Makers Do you see the pod abstraction as becoming important to components outside the Kubernetes platform? 2017-09-01T22:45:04Z Comment by The New Stack Makers Is there truly a danger of PaaS platform vendor lock in? 2017-09-01T22:44:30Z Comment by The New Stack Makers How is Kubernetes helping enterprises making the transition to 12-factor applications? 2017-09-01T22:44:03Z Comment by The New Stack Makers When a major adopter like Microsoft requests a back port in Kubernetes, what is it they're asking for, and how difficult is it for you to facilitate? 2017-09-01T22:43:38Z Comment by The New Stack Makers How CoreOS helps companies to distinguish which platform is best for them 2017-09-01T22:42:11Z
