Maintaining the Kubernetes Life Cycle
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 the Kubernetes open source container orchestration tool 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 Special Interest Group, in an interview for the latest episode of The New Stack Makers podcast. “We have a long code freeze and stabilization period to shake out any of the rough edges before a new version of Kubernetes lands.”
3:43: How CoreOS helps companies to distinguish which platform is best for its use cases.
7:23: 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?
10:17: How is Kubernetes helping enterprises making the transition to 12-factor applications?
16:04: Is there truly a danger of PaaS platform vendor lock in?
22:25: Do you see the pod abstraction as becoming important to components outside the Kubernetes platform?
24:39: Determining the CNCF’s responsibility for providing the bigger picture of the Kubernetes ecosystem.
Feature image via Pixabay.