Azure Kubernetes Service (AKS) Reviews

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.

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.

It is a hosting platform for creating web applications and deploying them. 

The serverless capability and auto scale feature are the most valuable. 

More control over Infra scanning can be introduced. 

I have been using Azure Kubernetes Service (AKS) for ten months. 

The stability of the solution needs improvement. I rate the stability a six out of ten.

It is a scalable solution but can be further improved based on the user requirements. Presently, a few hundred users are using the solution. I rate the scalability a seven out of ten.

The initial setup is easy. Some log maintenance is needed. I rate the setup an eight out of ten. 

The pricing of the solution is same as Azure Stack. 

It really depends upon the usage. If they really have the use case to go cloud, they can use it, but still, it is more applicable for people who want to get into software engineering and web development. Especially in the financial domain or e-commerce, where you would be relying on websites. 

I rate the overall solution a seven 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.

AKS is an orchestrator for containers you can manage within the Azure environment. It is the equivalent of AWS' EKS, and Google Cloud's equivalent is Kubernetes native service. AKS' main feature is that it helps you fetch, scale, and manage containers living within any sort of eco-space within Azure or other platforms to run them on demand. It provisions and scales containers on demand based on your configuration.

AKS as a service is very good when you need to leverage applications or functions with much variability in their usage because you're trying to be as efficient as you can with resources. AKS helps you distribute jobs along multiple nodes within clusters so you can handle larger loads without needing to provision additional infrastructure or set different autoscaling policies. AKS will provision and source all those containers on its own. The solution is very good when you need to scale constantly and distribute much more of the ingestion you're taking, whether through data jobs or serving up a certain application. AKS helps you scale horizontally, so you don't have to overload many requests into a larger machine, which eventually becomes costly.

One difference from Google Cloud is that AKS wants you to manage it from within the platform rather than more integratively or programmatically. But it just loses out because you have less access to it programmatically, with less technical or customizable access.

I've had very bad experiences with Microsoft's support. I rate their support somewhere around a five or a six out of ten. They do fine in assigning people to work on your cases, but their lead times for service are very slow. Even when you have critical incidents, you might be left hanging. That usually prompts you to resort to either Internet knowledge or just source yourself around the network of other Azure companies.

Neutral

We are consultants for multiple partners, so we usually adjust to whichever cloud provider they work with. In this case, we leverage Azure because the client already has an Azure infrastructure. Moving jobs for things like computing functions directly into Kubernetes is a decision that's mostly driven by how much we can manage scaling and how much we manage distributed computing. If we need a lot of flexibility on how much load our application will withstand, it's a solid move. It's so much easier than managing compute clusters, images, or provisioning infrastructure on your own. You can even make it work with other tools like TerraForm or CloudFormation. So you can set up the entire Kubernetes infrastructure without providing the resources until you get enough load. That's why Kubernetes has a strong use case overall for most modern applications and distributed processing.

Every container and elastic service on each of the clouds is very similar. Still, Azure offers an increased layer of security based on many permissions that can be handled through Active Directory. Security-wise, Azure is the better cloud and solves many of the inherent security issues that Kubernetes had originally. From there, I feel permission management is much better. The UI is simpler to understand.

I rate Azure Kubernetes Service a seven out of ten. It could be better, but it does its job very well.

AKS is a new technology for deploying a solution on microservice infrastructure. Most organizations are moving to this kind of solution. Its use case is for deployment, full-layer automation, and modernization technology. We are partners with Azure and have an enterprise agreement with them. 

A valuable aspect of this solution is the management feature monitored by the cloud service provider. 

Microsoft has an application firewall but it doesn't have all the good features and there is room for enhancement. The Microsoft in-grade controller has many issues that need to be solved. It's very important for us because we use Microsoft for 90% of our work and this is currently not a complete product. 

I've been using this solution for five years. 

The stability is good. 

The solution is flexible in terms of scalability. 

Customer service is very good with a prompt response time. They have a dedicated team to assist with support.

The initial setup is straightforward. Even if you go through the portal deployment, or the ARM template, it's very easy. Our deployment was large and scripting was done in the data form. I demonstrated it for the team on the non-production site and the application team carried out the same deployment on the production site with the help of automation.

The infrastructure part took three days because it was a total private cluster. The application deployment took longer, probably around six weeks, due to file and database-related issues. We have an in-house team with four dedicated people that provide maintenance. We also have operational staff that manages the pass services side and troubleshooting of AKS.

I think the ROI is very good. There are a lot of savings on the OS aspect. The container doesn't require the OS, it only needs some binary to run an application and that saves a lot of money. From a company perspective, it's very convenient.  

Licensing costs are reasonable, I believe somewhere around 30% cheaper than AWS.

Until they come up with a good ingress controller, I rate this product eight out of 10. 

We use the solution to deploy and manage containerized applications.

The solution's most valuable feature is its ability to integrate well with Azure Active Directory, Azure DevOps, and other Azure products. Also, it is easy to use and configure.

The solution's cost could be cheaper. Also, it is challenging to integrate the solution with different cloud services apart from Azure. They should improve these particular areas.

I have been the solution for a few months.

The solution is stable.

The solution is scalable.

The solution's initial setup process is straightforward. They provide proper documentation with steps required for deployment. It takes a few hours to complete.

Our in-house team executes deployment for basic applications. We need help from experts for complex implementations of the solution.

The solution's ROI depends on the use cases.

It is an expensive solution.

I recommend the solution to others and rate it as an eight.