Azure Kubernetes Service (AKS) honest review
Use Cases and Deployment Scope
We use Azure Kubernetes Service (AKS) to deploy container workloads mostly for microservices and other applications. It gives us flexibility in terms of scaling the compute based on application requirements. We can easily expand immediately rather thank waiting for someone to actually provision the compute. Also we are using Azure Kubernetes Service (AKS) to do a burst mode where we need some workloads to run for a short amount of time and then shutdown. Azure Kubernetes Service (AKS) perfectly fits into that.
Pros
- Container workloads
- Auto scaling
- Standard kubernetes deployment
- Easily integrate with Azure monitoring and Logging
Cons
- GUI on azure portal need to enhanced.
- The feature set should be matching with Openshift which is also kubernetes based
- Troubleshooting errors
Return on Investment
- It is cheap and able to deploy the same workloads as OCP but at lesser cost
- The ability to dynamically scale up and down makes this a preferred choice for container workloads
- The security and patching capabilities provided by Microsoft can be trusted
Usability
Alternatives Considered
Azure Red Hat OpenShift, Amazon Elastic Kubernetes Service (EKS), Google Kubernetes Engine and SUSE Rancher
Other Software Used
Azure Red Hat OpenShift, Azure Container Apps, Azure Container Registry, Azure Databricks, Azure Data Factory


