Choosing the right Kubernetes object for deploying workloads in Azure
I have published a blog series on AzureCAT guidance blog for choosing the right Kubernetes object for deploying workloads in Azure.
It consists of following posts:
- Part 1: This post covers setting up Kubernetes locally. It talks about minikube, kubectl, and so on.
- Part 2: This post covers setting up a Kubernetes cluster in Azure using Azure Container Service (ACS). It covers deployment options in Azure, deployment process, and connecting to a cluster by using a proxy.
- Part 3: This post is a high-level conceptual overview of Kubernetes. It covers various menu options in the Kubernetes dashboard.
- Part 4: This post covers deploying the SQL Server back-end, including choosing the right deployment object for running a database, the actual deployment process, and the interaction with SQL Server from SQL Server Management Studio.
- Part 5: This post covers deploying the ASP.Net Core web front-end, choosing the right deployment object, the actual deployment process, monitoring the cluster, and verification of the application working with the back-end.
Get started with this introductory post of the series.