Summary
In this chapter, we looked at how Microsoft Azure came to be, the history behind some of Microsoft’s container services, and how they eventually settled on AKS.
We then signed up for an Azure account and installed and configured the Azure CLI before launching our own AKS cluster. Once it was launched, we deployed the same workload we deployed to our GKE and Amazon EKS clusters.
Once the workload was deployed, we moved onto the Azure portal and looked at the options for gaining insights into our workload and cluster and some of the cluster management options.
We finally deleted the resources we launched and discussed how much the cluster would cost to run.
Out of the three public cloud services we have examined over the last three chapters, I personally would put Microsoft Azure AKS first; it has the most rounded and feature-rich offerings, alongside its ease of use. I would put Google’s offering, which we discussed in Chapter 15, Kubernetes Clusters...
