You are probably excited about containers just like I did when I first heard about them a few years ago. In the past, we would deploy our multi-container apps using Docker compose to a docker swarm and have it managed our containerized apps and this worked but also added a lot of complexity. I started looking for new ways to manage my containers and I came across Kubernetes. I just went … wow! I had a few posts previously talking about Kubernetes but they were mostly general discussions. This post is going to be a long one, from the planning step to the final way out. I will address why I choose such an infrastructure as we are moving through.
Deploying containerized apps to a Azure Kubernetes Service (AKS) cluster using the default settings in Azure isn’t that much tough as the tools handle most of the hard work for us. I recently discovered a scenario where I needed to connect my AKS cluster back to the on-prem resources. So I went ahead and created a AKS cluster via the Azure portal. In the creation step, I chose Azure VNet and this automatically set my cluster to use Azure Networking Interface (CNI).