Azure Kubernetes Service (AKS) Reviews

We used the solution to integrate banking pipelines for our customers. Also, we integrated Kibana into AKS, and from there, we deployed their parts. The solution's features, like machine learning models and analytical tools, have also helped us.

The solution's valuable features include in-built volume controllers, integration, container orchestration, monitoring, PSI drivers, Github, Gitlab, CI/CD, etc.

There are a lot of features that should be included with AKS. Also, the solution is still growing; thus, many things must be improved. We are still testing the solution, but they should provide better monitoring services. Along with it, they should include in-built DR features.

We have been using the solution for two years.

It is a stable solution.

It is a scalable solution.

We contacted the solution's customer service during the time of deployment. We also never needed the tech team's support, as the deployment is straightforward. The event architecture was required on our end; Microsoft doesn't help there. They provide basic help to establish the SaaS components.

I used Azure Virtual Desktop and Azure Migrate as well. Mostly, customers move their applications to AKS from the premise as they want active manageability of services. The other reason is credit plans. Customers prefer switching to services that offer them credit cards. Also, the pricing matters a lot. Even though the services are performing well, people opt for vendors offering a particular cloud that is low on cost.

The initial setup for testing purposes was easy. We just had to set some commands with a click, and it took around ten minutes to complete. During the final deployment, we required a code. It is a day long process.

The solution's pricing and licensing are structured on the basis of the use cases. Again, it depends on how many parts of a particular feature you require. There is a pricing calculator to get an aggregate cost based on the use cases, operating systems, storage capacity, etc. For Windows, the pricing depends on which side of the node you are using, i.e., Dual-core 4 GB RAM or Dual-core 8 GB RAM. It is possible to receive discounts on pricing with reserve incentives. In this case, it relies on how many VMs you run in the back end.

I advise others to initiate with basic services of the solution and then explore further. It is easy to maintain the solution. We can view and monitor all the processes through its monitoring feature. I rate the solution as a nine.

We use AKS for most of our Azure cloud services, including performance testing and other applications we deploy on an Azure Kubernetes cluster. 

AKS is easy to use. We can scale up and down as needed with AKS, which saves us money on our cloud costs. 

I would like to see Azure implement something like the K9 terminal for interacting with Kubernetes clusters. It's a user-friendly CLI interface.

I have used AKS for around six months.

I rate AKS nine out of 10 for stability. 

I rate AKS eight out of 10 for scalability. 

The initial deployment was challenging because I had trouble understanding the documentation. I didn't have this issue with Google Cloud Platform or AWS, but Azure seemed a little difficult. 

I rate Azure Kubernetes Service eight out of 10. I strongly recommend it. 

Our primary use case is to host our applications for Azure Cloud, rather than hosting the application on our on-premises infrastructure. We are hosting our applications in Kubernetes in Azure Cloud. I work for a product waste company, central components wherein during the weekend the traffic is more and during the weekdays the traffic is less. During festival time, the web traffic is more. So we need some kind of automatic solution. When the web traffic is more, the Kubernetes Service auto-scales, increasing the number of resources like horizontal scaling or vertical scaling. And if the web traffic is less, it descales, like releasing some of the resources. Kubernetes helps in autoscaling and that is why we migrated from on-premises to Kubernetes.

The most valuable feature is the autoscaling and self-healing. In our application, we have multiple replicas. If one of the replicas is not working due to anything, a new replica is automatically created.

I would like to see a graphical user interface.

I have been working with Azure Kubernetes Service (AKS) for the past three years.

There is excellent stability.

There is above-average scalability and we do have plans to increase our usage.

The initial setup is complex and not straightforward. I think it would be helpful if we had some type of script for the installation to make it easier.

We used a vendor team lens from the Mirantis company.

Minikube is one small Kubernetes cluster. With minikube, we can install this on our local laptop and we can practice. So to know Kubernetes, we have a concept of minikube which can be installed on a local laptop and we can practice Kubernetes commands. On a scale of one to ten, I would rate Azure Kubernetes Service (AKS) an eight.

Our customers use the solution to develop their business applications.

The solution's dashboard integration with Kubernetes helps us manage workloads easily.

They should work on improving the solution's integration with API. They should add an option for installing open-source tools such as Kube-State-Metrics to leverage the community.

We have been using the solution for three years.

The solution is more stable than EKS. Although, we face some issues while upgrading it. I rate its stability as an eight.

Our customers have around 50-60 developers using the solution in their organizations. I rate its scalability as an eight.

The solution's customer service team resolves the technical issues accurately. But it takes a long time to reply to queries.

The solution is simple to install compared to AWS, which needs many prerequisites to follow.

The solution is expensive compared to other vendors. I rate its pricing as a five.

I have evaluated IBM Cloud, GKE, and AWS. They all are similar to AKS and have a few advantages over it. But AKS is better than them in terms of implementation, scalability, accessibility, and overall services.

The solution is excellent. But sometimes, it couldn't provide specific metrics. In addition, integrating it with Azure's metric app also fails to generate the expected results.

I rate the solution as a seven.

The most valuable features of AKS are scalability, deployability, and automation.

Configuration management and troubleshooting performance issues are difficult to solve and could be made easier. 

I have been using Azure Kubernetes Service (AKS) for approximately one and a half years.

There are some performance issues with the stability. There is some fine-tuning needed.

I rate the stability of AKS a seven out of ten.

The solution is scalable.

Small to medium-sized businesses are best suited for AKS.

I rate the scalability of AKS a nine out of ten.

The support is excellent.

I rate the support AKS an eight out of ten.

Positive

The initial setup can be complex and took a total of four weeks. However, the incremental deployment took a couple of days.

In the first step of implementation, we do an estimation and identify all of our independent modules and packaging needed.

I rate the initial setup of AKS a three out of ten.

The price of AKS is expensive. We pay approximately $10,000 monthly.

My advice for others is to focus more on packaging the individual models and cables before going to where the solution is situated.

I rate AKS a six out of ten.

I am using AKS on a Cosmos DB database. AKS is similar to AWS in stability and scalability, but when used with C#, AKS is easier to deploy and better to use because I use .NET applications.

The documentation makes it easier to deploy AKS, so it is the most valuable feature.

The onboarding process could be improved. For example, when you open Azure's main port, it is not very easy to access the servers because you need to put your mail and password, and sometimes you need to configure the authenticator. Depending on the case, this could be a problem.

I have been using AKS for two years, and I am using the latest version.

The solution is stable.

The solution is scalable.

The customer support has been good.

The initial setup was very easy.

I have not seen a return on investment since I have only used the solution in my company for two months.

The solution is not very expensive. It is expensive when used on the Cosmos DB database.

The solution has good documentation and is easy to use and deploy. AKS is a good place to start your business. I rate the solution a ten out of ten.

I use the solution for infrastructure services on platforms. It can be used for running virtual instances on Azure.

Integration and automation are the best features of the solution. It is interesting to see what it could deliver by integrating all the services.

The product should make the initial setup easier. The product should provide an online format where I can see, read, study and research it on demand.

I have been using the solution for around five years.

I don't see any stability issues with the multiple servers integrated into Azure.

Scalability is one of the top benefits when you migrate to the cloud. We can go directly from 20 users to 10,000 users.

The initial setup is complex.

Nothing in Azure is as easy as plug-and-play. Most of the time, the product is cloud-based. There are on-premise solutions for very specific cases. As a representative of cybersecurity operations, I have to do research and read the manuals. Overall, I rate the product an eight out of ten.

We download the internal website to showcase our organization’s development and products and present it to customers in a web application.

Each component is deployed as a microservice in Kubernetes. The web application is deployed in Azure Kubernetes Service. Everything runs inside the Kubernetes only.

The main features of Azure Kubernetes Service are how it deploys and manages microservices and enables them to communicate. AKS can also group, classify, and log data. AKS makes it easy to deploy, maintain, and communicate between microservices.

The solution could provide more logging mechanisms and a good user interface.

I have been using Azure Kubernetes service for three years.

The product is stable.

AKS has been used for six years to deploy and manage containerized applications in production, development, and testing environments. AKS is a stable and reliable service, and we have not had any issues with it.

Between 100 to 1,000 internal customers are opening the site and logging in to see the feature labeled location, demo, reporting, etc. Scalability depends on what we are scaling. For example, we have two nodes for Development, four in production, and three for backup.

When there were some hiccups, we took up a Microsoft support ticket. They're very good and help us a lot to solve the issues. I have worked with them a couple of times.

The initial setup is very easy. There are seven to eight tabs. If you select all the tabs and go for a deployment, it may take up to ten to fifteen minutes to complete.

Generally, I write my scripts for Deployment. Sometimes, we use partial or batch scripting, using HCLA comments to parameterize the scripts based on the requirements. Otherwise, you can use Terraform scripting to deploy.

I did the deployment by myself. We generally use a third-party team to get their input, but I initially used open-source tools with AKS. I used these tools to write steps that can be taken and everything.

We have taken a three-year contract.

Kubernetes is simple. If somebody wants to divert their applications into multiple pieces broadly and maintain them for a longer duration and accessible support, AKS is a web application that hosts them into containers. AKS also provides good support.

Overall, I rate the solution an eight out of ten.