COPENHAGEN, Denmark — At the Kubecon and CloudNativecon Europe 2018 day two keynotes on May 3, speakers discussed Kubernetes success stories and what's coming next.
Aparna Sinha, group product manager at Google, outlined the core areas of concern that are leading feature development in future Kubernetes releases. She noted the top three issues the Kubernetes community is working on are security, application enablement and providing a better experience for developers.
Sinha said a key goal for Kubernetes is to make enterprise software that is as agile and efficient as consumer software.
For security, she noted multiple items that have landed in recent Kubernetes releases, including PodSecurity Policy, Role-Based Access Control and Encrypted Secrets. To help further improve security, Google announced its gVisor sandboxed container effort on May 2.
Stateless Apps and Application Operators in Kubernetes
Originally Kubernetes was all about running stateless apps, but the goal moving forward is to make sure it is a really good platform for stateful apps as well. Sinha said the Kubernetes community is working to make application automation easier as well, which is where the application operators technology comes in.
"Application operators automate lifecycle operations," Sinha said.
Those lifecycle operations include backup restore, monitoring and scaling. The goal is to enable organizations to deploy complex stateful apps in less than 10 mins.
Improving the Kubernetes Developer Experience
Sinha demonstrated a new effort called the Skaffold project, which is all about making it easier for developers. With Skaffold, developers can use a container builder that will then easily integrate with a container registry, making the application easier to deploy.
Overall, Sinha said the roadmap for the Kubernetes project is based on user adoption.
"We're doing things both complex and simple to make it more usable for more audiences," she said.
User Experiences Working with 'Boring' Kubernetes
Sarah Wells, Technical Director for Operations and Reliability, at the Financial Times, used her time on stage to detail how her organization migrated to Kubernetes.
Wells explained that the Financial Times (FT) started using Docker in 2015 and initially had its own approach for orchestration and deployment. What FT realized is it needed to move to an orchestration technology that was easier to maintain and that "is boring."
Wells said choosing boring technology is a good thing in this case, as it means lots of companies are using the same thing and it just works.
"The Financial Times is not a cluster orchestration company; we're a news company, and that's where we should focus our innovation," she said.
Sean Michael Kerner is a senior editor at ServerWatch and InternetNews.com. Follow him on Twitter @TechJournalist.