<!-- .slide: data-background="images/chuttersnap-9cCeS9Sg6nU-unsplash.jpg" style="padding: 1em 1em 1em 1em; color: white; background: rgba(0, 0, 0, 0.5); width: 75%; margin: auto; position: absolute; top: 15%; bottom: 15%; left: 0; right: 0;" --> <img src="images/NicholasDille.jpg" /> <!-- .element: style="width: 22%; float: left; border-radius: 8px; margin-left: 1em; margin-right: 1em;" --> # Kubernetes - More than a container orchestrator Nicholas Dille, Haufe Group ### <i class="fab fa-docker" style="width: 1.5em; text-align: center;"></i> Docker Captain <i class="fab fa-windows" style="width: 1.5em; text-align: center;"></i> Microsoft MVP ### <i class="fab fa-twitter" style="width: 1.5em; text-align: center;"></i> @nicholasdille  <!-- .element: style="width: 20%; float: right;" -->  <!-- .element: style="width: 20%; float: right;" -->

## Container orchestration ### Because one host is not enough Containers are scheduled across multiple nodes Network connectivity between nodes Capacity and resources are managed ### This is commodity

## Recap  <!-- .element: style="float: right; width: 25%;" --> Transparency through events Controllers watch resources and act on changes Operators manage application lifecycle You can write them in shell... ...but should you?! ### Questions? ### Slides are available [<i class="fab fa-github" style="width: 1.5em; text-align: center;"></i>](https://github.com/nicholasdille/container-slides/releases/tag/20211118)