He said it allows customers to “very quickly offer a better environment for developers or dev and test, as well as production, because they can go from Day Zero and the end of that five-minute cluster creation time, and actually have Day 2 done as well.”
The new mode “does free up teams to focus on the actual workloads and less on managing Kubernetes clusters. With Autopilot, businesses still get the benefits of Kubernetes, but without all of the routine management and maintenance work that comes with that. And that’s definitely a trend we’ve been seeing as the Kubernetes ecosystem has evolved. Few companies, after all, see their ability to effectively manage Kubernetes as their real competitive differentiator.”
Autopilot is described as an optional mode – the “standard experience” is still an option for users who want to customize configurations and manually provision and manage their infrastructure themselves.
It simply lowers the bar of entry for enterprises interested in using containers, according to Bradstock.
“Autopilot is more about simplifying the entire platform people work on when they want to leverage the Kubernetes ecosystem, be a lot more in control and have a whole bunch of apps running within one environment,” he said.
Tuning Kubernetes for Services
Audio streaming service Spotify recently developed a monitoring tool that simplifies the management of services deployed on Kubernetes. Matthew Clarke, Senior Infrastructure Engineer at Spotify, wrote on The New Stack that the tool is a core feature of Backstage, Spotify’s open platform for building developer portals.
“If you’re building a service today, you’re likely deploying it as a container, which is inside a pod, which is inside a cluster (alongside a bunch of other services that don’t belong to you), with deployments on different clusters spinning up and down all around the world,” said Clarke. “It can be hard to keep track of everything.”
He explained that while Kubernetes has democratized container technology and has been widely adopted, many of the tools designed to reduce complexity have been focused primarily on the management tasks of cluster administrators.
When containers were new, “cluster admins and service owners were one and the same: the people who built a cluster were usually the same people who owned the services that ran in the cluster. That’s not how it is today,” said Clarke.