

Operations teams worry about keeping the cluster online and scheduling pods.īut from my perspective, adopting and migrating cloud native technologies is the perfect time to resist that temptation and ensure application developers have the right kind of access to your infrastructure.

Because of the simplicity and best practices they bring to the operations side of a technology stack, it’s tempting to use them as an excuse to take a step back from the DevOps culture and rebuild some of the walls.įrontend developers worry about implementing the design system and dealing with APIs. Kubernetes, like most cloud native technologies, hides complexity behind a few layers of abstraction.

If the Kubernetes cluster manages all the operations so well on its own - with declarative configuration and self-healing - organizations start to ask, “Why should developers need to know anything about operations anymore?” If DevOps was meant to encourage transparency and collaboration, Kubernetes often becomes a convenient excuse for organizations who haven’t yet fully embraced the culture.
