When you’re first looking at Kubernetes applications, it’s common to see a simple scenario that may include several pieces — but not explicit dependencies. But what happens when you have an application that does include dependencies. For example, what happens if the database must always be configured before the web servers, and so on? It’s common for situations to arise in which resources need to be created in a specific order, which isn’t easily accomodated with today’s templates.
To solve this problem, Mirantis Development Manager for Kubernetes projects Piotr Siwczak explained the concept and implementation of the Kubernetes AppController, which enables you to orchestrate and manage the creation of dependences for a multi-part application as part of the deployment process.
You can see the entire presentation below: