Azure Kubernetes Service (AKS)

Simplistic management procedure allowing users to control operations across centrally specified nodes. Scalability across different data and company sizes on autopilot helps bring down overcharges under control. Advanced security protocols make way for collaboration from anywhere, anytime.

Continuous Integration and Deployment were effortless in AKS, Azure threat detection modules made sure all the AKS clusters were secure and compliant with key security standards. Since we are a Microsoft factory, it was easy to manage and scale applications.

The main thing that I like about AKS is its deep integration features with other Azure environments such as Azure Monitors, VMs, Logic apps, DevOps etc. I also like the features about how it abstracts much of the operational complexity of Kubernetes. Automated upgrades, managed pools, built in monitoring, and seamless integration features also add more strengths to this product.

Stringent one-time configurations with no future backtracking induces lack of customization. Non-consistent delivery performance at the gateway node end sometimes.

The main challenge around AKS was we needed to always update the clusters manually, which interim was relatively easy and automatic with its competitors. If we are setting a new policy, then this new policy cannot be applied to the existing clusters. This was a challenge, as we need a lot of manual intervention in his kind of situation.

While AKS is powerful, the biggest drawback is that upgrades and troubleshooting can be challenging as it may require advanced technical knowledge. Some operations, such as cluster upgrades, node pool changes, and networking configuration can be more complex and sometimes disruptive.