Azure Kubernetes Service (AKS) Reviews

We are using Azure Kubernetes Service as a customer. I cannot detail all the products and technologies we are using.

There isn't one specific feature of Azure Kubernetes Service that I can name as most valuable. It's part of a strategic solution yet I don't see an advantage compared to our personal cloud solution. Our move to Azure did not bring any cost reductions.

My primary use case is building and deploying solutions using multiple Azure services. I combine these services to build systems on Azure Kubernetes Service (AKS). Since I work mainly as a back-end developer, my focus is on deploying these solutions within AKS environments.

My organization wants to migrate to Azure Cloud for better scalability in Kubernetes environments. AKS allows us to set up servers with unlimited resources and scale them based on demand, without worrying about internal server management.

The requests get processed within seconds. Earlier, it used to take around four to five minutes. 

The product has  built-in functionality that checks whether the service is available or not. In case the service is down, the tool will create a new instance by default. Hence, the web API will be always up irrespective of the server or the situation. 

I need to configure the availability of my applications, and the Azure Kubernetes Service makes this easier to manage. Instead of having 20 separate computers with 20 separate apps, I can use one computer with virtualized applications, saving time and effort with the administration.

The most valuable feature of the solution is the diagnostic service.

Our use case is for any microservice that requires a Kubernetes platform for deployment. But primarily, my reason for using it was to develop a tool for our clients to migrate their deployments from Pivotal Cloud Foundry, which is now out of support. I wrote a tool to automatically convert Pivotal configurations into Kubernetes and then deployed them on Azure Kubernetes Service for testing the mapping and tool output.

So it's more of a migration from Pivotal Cloud Foundry to Kubernetes and deployments, with Azure AKS as the target platform.

For most of our deployments, we utilize Azure DevOps pipelines. It provides a seamless experience with a fantastic console and user interface. You can configure the pipeline steps, including pulling code from the Git repository, triggering execution, building the container image, and pushing it to the Kubernetes clusters. All of this can be done on a single screen, making configuration easy and intuitive for developers.

I am using Azure Kubernetes Service (AKS) for enterprise applications. These applications are divided into microservices, and we have multiple environments hosting various applications within Kubernetes.

The integration with Azure's security capabilities is very good. The Azure-managed identity and integration with the Azure application gateway for App Ingress are valuable features. Additionally, it is a very stable tool.

I use the solution for micro-services deployment. Azure Kubernetes Service (AKS) has helped reduce downtime. 

I have used almost all the features of Azure Kubernetes Service (AKS), but the Front Door and Service Bus are the most vital features. Our organization also uses Azure Database, Insights, Log Workspace, and Azure Functions.  

The solution is used to deploy applications in a very highly scalable model. Any customer can deploy the application. They won't have to worry about the scalability and reliability of the VM. Most things are taken care of by AKS.

Containerization of the applications is the most valuable feature. It needs effort at the code level to decouple the existing codes and put different templates in different clusters. However, once it is done, the tool is highly scalable and reliable.