Establishing Best Practices for Adopting Kubernetes
Establishing best practices for emerging technologies is a task that many will argue is impossible. But it’s still important for you to identify how teams are consistently solving problems, even when the technology changes around them. With Kubernetes, there are many best practices whose emergence may provide keys for assessing Kubernetes’ future.
In this edition of The New Stack Makers, we spoke with Justin Mound, CTO, and Eric Hole, site reliability engineer, at ReactiveOps. We asked them about the best practices that they perceive as emerging around Kubernetes, based on their interaction with customers that are adopting and utilizing the platform. While many of these best practices are firming up within the Kubernetes community, there are still a number of pain points, such as storage persistence and secrets management. We talked about how ReactiveOps is solving some of these problems with customers, and which problems they expect to be resolved as tooling in the Kubernetes ecosystem evolves.
1:47: An introduction to ReactiveOps.
3:15: How customers are receiving the ReactiveOps DevOps-as-a-Service model.
5:20: Exploring ReactiveOps Site Reliability Engineering experience as a boon to customers.
10:57: What is some of the major roadblocks you’re seeing from an operations standpoint with most of your customers?
19:23: Creating your own best practices.
23:15: Discussing KOPS and what’s next for ReactiveOps.
Feature image via Pixabay.