Teams turn to containers and Kubernetes for many, perfectly good reasons. Most importantly to enable them to sustainably increase application delivery velocity. Translated into plain English: To get more done with less drama.
But when getting started with Kubernetes, like with any new technology, questions arise about how things should be done. Does your current way of doing things still apply or is there a better way? Do you limit or worse, eliminate the benefits of using Kubernetes if you make a mistake now?
This guide describes a way to manage infrastructure and applications with a focus on enabling constant change. But to achieve this we have to rethink various aspects of our stack.
Starting with clusters & environments, making sure you can work on infrastructure and applications at the same time, without one blocking the other. Continuing with reliable and sustainable infrastructure automation.
Next, we'll take a look at how to handle teams and namespaces and how to setup authentication and authorization in a way that enables moving fast and enforces a culture of shared responsibility and mutual trust.
Finally, we'll venture into declarative application management and how to handle manifests sustainably.
Overall, this guide tries to answer questions many teams face trying to make application delivery more sustainable and predictable.
So, if you remember one thing from this introduction, remember that in order to enable change you have to change your infrastructure architecture and workflows. Keep too much of the legacy architecture and approach and you may end up limiting the benefits you gain from using Kubernetes.
Lets get started learning how to maintain constantly changing infrastructure and applications with multiple teams without stepping on each other's toes.