Azure Kubernetes Service (AKS) Reviews

We are a customer from a government organization. The solution is used for products related to machine learning. Since we are a government organization, we do not see any profit.

We have multiple solutions such as SimpliVity, Nutanix, and DXRail, which are all part of our Ansible-based system. It gives us more confidence and we can control our groups effectively.

The solution is not particularly user-friendly for novice administrators, making it challenging to understand certain aspects. Templates are not readily available, requiring users to build their own worksheets and everything from scratch. This is a main decentralization we observe compared to VMware.

We have tested various solutions including Rancher, RHEL, Canonical from SUSE, and the bare metal version from RHEL direct. Since pricing is not a major concern, we chose the best fit for our application, which was specifically designed for this particular platform.

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.

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.

We use the product mostly for development purposes. Some are in the pilot phase for customer usage, however, there's no real production workload active right now on these services. It is mostly for dev test and pilot purposes.

It has made life much easier because I don't have to manage Kubernetes myself. It saves time and efforts on the infrastructure side, letting me hand off service administration jobs to junior admins without the fear of them screwing up the environment.

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 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.  

We began utilizing AKS this year. Our aim is to embrace cloud-native practices, and Kubernetes is an excellent choice for achieving that. Additionally, Nicola seems to be well-suited for our needs. Therefore, we decided to adopt Kubernetes as our platform for software development. This allows us to enable the app team to effortlessly create infrastructure using the infrastructure scope. While we still rely on virtual machines, it is solely for the purpose of visualization, not for hosting the service. Our focus remains on building specialized software.

AKS provides a convenient solution for developers. When working locally, developers can leverage containerization technologies like Docker and Docker Compose. However, when it comes to testing environments, the Infrastructure as Code feature of AKS allows for easy setup of the entire testing environment. The team can collaborate and make necessary adjustments, while developers can switch back to their local environment whenever needed. The staging environment follows a similar pattern, as the same template can be applied, enabling quick hosting of the entire infrastructure. This approach saves a significant amount of time in infrastructure creation. Additionally, it adds another layer for the DevOps team, reducing their burden of dealing with cloud infrastructure details and allowing them to focus on capabilities. This streamlined process can be replicated across multiple projects, making it a valuable aspect of AKS.