Azure Kubernetes Service (AKS) Reviews

I use the product for the environments in the company, specifically for the environments in production, QA, and development.

I used it in the finance industry at a bank. Now I have moved to another bank, which is the biggest.

For Azure Kubernetes Service (AKS), we only used it to orchestrate the Kubernetes pods. We didn't use the other features. We only used the environment to start our application.

I utilized the automatic scaling capabilities.

The integration with Azure Active Directory helped with the security of our applications.

I think Amazon EKS is better. EKS is the best because there are many features to use for scaling and to control the environments.

I am not sure about areas that could be improved.

I have limited knowledge about AWS EKS because I started working here 20 days ago.

I started with EKS in AWS about one month ago. With Azure Kubernetes Service (AKS), I worked for three years.

It's very stable, and the support is satisfactory. I don't have significant problems with the environments, which I consider good.

The automatic scaling helped with scalability.

I would score Microsoft support as 10 out of 10.

They are very fast to respond and begin analysis to resolve problems, which is why I give them a perfect score.

Positive

I have experience with both Amazon and Azure products, but now I don't work with Azure anymore. I changed jobs and work at C6 Bank, focusing only on Kubernetes and Service Mesh. I stopped working with storage and Azure.

The initial setup is very easy.

I would rate it 10 regarding how easy it is to set up.

My company was a partner with Microsoft.

It helped through the health of our environments and the costs, assisting with FinOps.

The solution is very expensive in my opinion.

The built-in monitoring can be expensive as well.

We didn't use the built-in logging from Azure Kubernetes Service (AKS). Sometimes we enable Log Analytics, but it's very expensive and only enabled if necessary to analyze significant problems.

My company was a partner with Microsoft.

In the last year, I had more experience with Azure products but did not work with them.

I am familiar with Red Hat Kubernetes, but we're using EKS on AWS.

I used Linux containers and did not use Windows containers. It was able to containerize and deploy those containers easily.

It provided more security and was easier to work with the integration with Azure Monitor and Azure Security Center.

I don't know about improvements regarding the price, but they could improve it.

I worked with Amazon EKS.

I rate this solution 7 out of 10.

My main use case for Azure Kubernetes Service (AKS) is hosting a Comark website on it. In addition to hosting a Comark website, I have started using Azure Kubernetes Service (AKS) for hosting AI workloads as well.

Azure Kubernetes Service (AKS) positively impacts my organization by helping us reduce costs; we run multiple microservices under one Azure Kubernetes Service (AKS) cluster using different namespaces, isolating each application and making management easy with beneficial add-ons.

I see significant improvements in cost savings, deployment speed, and reduced manual work across all three metrics with Azure Kubernetes Service (AKS). Using spot instances in lower environments expedites deployments with a microservices approach. Integrations with other systems and automation are seamless; we follow a GitOps approach using tools like Argo CD and Flux CD for automated deployments.

The best features Azure Kubernetes Service (AKS) offers include compatibility with existing MS infrastructure, ease of managing access through AD, and accessible RBACs. On top of that, it provides many add-on features such as Prometheus, service mesh, and other tools, with good support and easy upgrades that save us from downtime.

The ease of managing access through AD in Azure Kubernetes Service (AKS) helps my team day-to-day. Without AD management and RBACs, generating certificates, approving CSRs, and using those certificates to access Azure Kubernetes Service (AKS) becomes very troublesome and complicated, especially for new team members. This functionality makes that part very easy. Additionally, applications hosted within Azure have seamless connectivity to databases, making it easier to onboard numerous applications, handle networks, and troubleshoot. Regarding upgrades, Azure Kubernetes Service (AKS) frequently provides updates, which simplifies the process significantly compared to managing bare metal systems.

I do not see any specific areas for improvement in Azure Kubernetes Service (AKS), except for the kind of support they provide. At times, the engineers I connect with are not very skilled.

I have been using Azure Kubernetes Service (AKS) for more than four years.

Azure Kubernetes Service (AKS) is very stable; I rarely see any hiccups.

The scalability of Azure Kubernetes Service (AKS) is one of the best I have experienced in the market, with node auto-scalers that quickly respond to high workloads, supported by capabilities such as KEDA and horizontal pod auto-scaling.

Customer support for Azure Kubernetes Service (AKS) is typically good, but in some instances where technical expertise is required, I sometimes feel I know more than the support personnel.

Positive

I started my career with Azure Kubernetes Service (AKS) and did not previously use a different solution. I was not part of the evaluation team before choosing Azure Kubernetes Service (AKS) and worked on bare metal systems. I have heard that GKE is not favorable, but I cannot speak from experience as certain capabilities aligned with our workloads led us to choose Azure Kubernetes Service (AKS).

We see a return on investment with Azure Kubernetes Service (AKS), as we no longer manage the control plane ourselves, which saves us a lot of time and employee effort. We also do not have to manage the OS on underlying nodes or worry about upgrades and security patching, as those are taken care of automatically.

My experience with pricing, setup costs, and licensing for Azure Kubernetes Service (AKS) involves booking quotas for commitments of three to five years to receive significant discounts, along with using Azure Advisor, which helps identify opportunities for cost savings by showing where we spend the most money.

I would rate Azure Kubernetes Service (AKS) at a nine out of ten. I deduct one point for customer support, as seventy percent of the time I interact with lower-skilled candidates for troubleshooting issues.

Azure Kubernetes Service (AKS) is deployed in a public cloud within my organization, hosted on Azure Cloud, where we restrict access through VPNs and authorized IP ranges, ensuring that no one can directly connect to API servers. We also have our Azure Kubernetes Service (AKS) clusters peered in different regions, acting as both an active site and a disaster recovery site.

For those looking into using Azure Kubernetes Service (AKS), I advise considering the expected size and infrastructure of your system before setting up virtual networks, as using smaller subnets can lead to scalability challenges. Starting with Azure CNI overlay can prevent these issues.

I find it satisfactory that Azure Kubernetes Service (AKS) ships upgrades frequently, helping us stay on top of technology, keep our stack updated, and achieve stable results.

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.

The main area for improvement is pricing. It is costly compared to other solutions such as Canonical. When purchasing support directly from RHEL, the price is significantly high.

We have been using the products since March, approximately 3 months.

It has not been enough time to properly evaluate the products as we have only been using them for 2-3 months. We need to wait at least 6-8 months to make confident comments about stability.

The customer service is straightforward.

Neutral

We previously worked with different products, not OpenText products, but we are not currently using them.

The initial setup was satisfactory, which influenced our purchase decision. We completed the POC and initial studies before making the purchase.

We have a managed project with professional services from RHEL and Azure.

The solution has great support and is flexible to understand. We build and provide it to stakeholders who mainly manage it, with only the fashion part being ordered.

Regarding support response times, there are some timing issues due to our country location. While our SLA is one hour and they usually respond within 45 minutes, we expected quicker responses. Based on SLA compliance, we would rate it 8 out of 10.

We are using on-premises Kubernetes from RHEL Openshift.

Overall rating: 7 out of 10.

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.

I am not impressed with the support services from Microsoft yet. Even being a big customer, I would rate the support four out of ten. The costs are rising rapidly, and we have not seen any cost reductions by moving to Azure.

We have been using Azure Kubernetes Service for approximately a year.

I would rate the stability of Azure Kubernetes Service eight out of ten.

We are not yet fully public cloud-native, however, Azure Kubernetes Service promises interesting scalability and flexibility for the future.

The customer service is not satisfying. I would rate it four out of ten. It's not very good.

Positive

We previously used our own cloud solution built on top of IBM. We decided to move to Azure due to cost considerations and an initial strategy to transition to the public cloud.

The initial setup was time-consuming and involved consultants. We started with one implementation, moved to our own solution on Azure, and later shifted to a policy-based model.

We made use of many Microsoft consultants during the implementation phase.

In terms of return on investment, the costs seem to have increased compared to our own data center solutions.

Transitioning to Azure did not bring cost reductions; in fact, costs are rising rapidly. We have not seen any savings compared to our previous setup.

We used our own cloud solution built on IBM and currently employ solutions from Cisco and Oracle.

It's too early to make recommendations as it depends on the organization's plan and goals.

I'd rate the solution seven out of ten.

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 most valuable features of Azure Kubernetes Service are its integration with Kubernetes, offering similar features for a seamless experience. AKS provides the auto-scale feature and manages the master node, allowing me to focus on the worker nodes only. This removes the need for managing master node updates or operating systems.

One improvement I'd like to see is a better user interface for developers, enabling easier operation without relying heavily on command lines.

I have been working with Azure Kubernetes Service for almost two years.

I haven't experienced any specific issues with the stability of AKS. From my usage, I would rate its stability as eight to nine out of ten.

AKS offers excellent scalability due to its adaptation from Kubernetes. The auto-scale feature allows for optimized resource usage, focusing only on worker nodes. I rate its scalability as nine out of ten.

I did not participate in the initial setup of Azure Kubernetes Service.

I am involved in writing and deploying scripts for applications via the deployment service.

The pricing for Azure Kubernetes Service seems to be around the average, which I would rate as a five out of ten.

For new users evaluating AKS, if you want a platform where you don't need to manage OS updates or operations, AKS might be a good choice. It allows you to focus on your work and provides very effective scaling features. 

Overall, I rate AKS as a seven out of ten.

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 cost of Azure Kubernetes Service (AKS) is extremely high. 

I have been using Azure Kubernetes Service (AKS) for four years. 

Based on the support, documentation and user-friendly interface of the solution, I would rate the stability a nine out of ten. 

Azure Kubernetes Service (AKS) is very easy to scale, and in our organization, we are using VMSS for scaling. The product is more suited for enterprise-level companies. 

I would rate the tech support an eight out of ten. As our company has availed a basic plan of Azure Kubernetes Service (AKS), the response time is longer in a few cases where I have resolved the issues on my own through extensive research. But in most cases, I have received effective help from the support team which I truly appreciate. 

Positive

I have worked on the solution's setup for multiple environments and found the deployment to be easy and hassle-free. When using Terraform to configure the solution, I faced some issues at one point, which were resolved by the support team of Azure Kubernetes Service (AKS). 

At our company, we follow a complete cloud-based model for Azure Kubernetes Service (AKS). 

I have worked with Azure and AWS solutions, but comparatively, the price of Azure products is much greater. Azure Kubernetes Service (AKS) is an expensive solution, and our organization's clients have complained about it. 

Azure Kubernetes Service (AKS) is a bit expensive compared to AWS solutions, but other than that, there are no advantages to choosing another solution. 

Azure Kubernetes Service (AKS) can be easily integrated with other tools of the Azure environment. For our company projects where the solution is being used, I have onboarded them at a later stage, but rarely have I had to seek help from the support team. 

Documentations for the product are easily available. I would overall rate Azure Kubernetes Service (AKS) a nine out of ten. I would definitely recommend the product to other users. For enterprise projects, where the clients have a heavy budget, Azure Kubernetes Service (AKS) can be adopted without any doubt. 

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.

If any customer uses a traditional code, the code-level changes take a lot of time. Once that is done, there are no challenges. After that, it is pretty straightforward. It would be good if the vendor could provide an out-of-the-box solution that would enable customers to deploy things directly without worrying about code-level changes. Then, the customer does not have to worry about developing the solution again or adding new libraries to the existing code to make the code cloud-ready.

I have been using the solution for three to four years.

The tool is stable. I rate the stability a nine out of ten.

AKS is a highly scalable model. I rate the scalability a nine out of ten. Almost 60% of our customers are using the solution. Apart from the SMB customers, all the others are using the product.

I did not face any major challenges. I faced issues once or twice, and it was sorted in a day or two. The support is good.

The time taken for deployment depends on the use cases. The deployment can take 10 to 30 days, depending on the environment and solution we are working with.

The return on investment is not that high. Our customer has to change the codes to move to AKS. Convincing the management about the ROI is pretty tough in such scenarios. However, the tool will produce a good ROI in the long run.

From a licensing perspective, moving from a traditional model to a new one won't make much difference because the same virtual machine is being used in the backend. We are just adding a layer that gives the organization more flexibility and manageability. The solution does not cost much.

The customers have to pay an extra $100 or $150 based on their number of clusters. It won't make much of a difference for any environment. If an organization pays $100 for a normal infrastructure, it will hardly cost 10% extra with added manageability and scalability. It would hardly make a dent in the pocket.

Azure Kubernetes Service is a good solution for any organisation wanting to opt for containerization. AI can be integrated with the application. Overall, I rate the product a nine out of ten.

I work for cloud transformation with Azure Kubernetes Service (AKS) for major UI transformations of products and services.

Azure Kubernetes Service (AKS) operates on a pay-as-you-go model, so my company can get whatever we require from the tool.

Azure Kubernetes Service (AKS) is not up to optimal standards when it comes to capturing logs and visualization. The aforementioned area can be considered for improvement in the product.

I have experience with Azure Kubernetes Service (AKS) for two years. My role in the company is to manage all the architects and resources. I am an implementer who develops applications and deploys them.

Stability-wise, I rate the solution an eight out of ten.

Scalability-wise, I rate the solution a five out of ten.

My clients who use the product are mostly medium-sized businesses.

I rate the technical support an eight out of ten.

Positive

I rate the initial setup phase of Azure Kubernetes Service (AKS) as a three on a scale of one to ten, where one is difficult, and ten is easy.

The solution is deployed on the cloud.

The solution can be deployed in thirty to forty minutes. After the tool's process was streamlined in our company, it could be deployed in only five to ten minutes.

The product is expensive.

The product supports our company's container orchestration needs since we mainly use it for management and deployment purposes while also covering areas like orchestration and auto-scaling.

The product serves the purpose of helping streamline our company's application deployment and scaling processes.

Speaking about the feature of the product that has been most impactful in managing our Kubernetes-based environment, I would say that I am not into the deployment part of Azure Kubernetes Service (AKS) since I have to focus more on strategy implementation.

Azure Kubernetes Service (AKS) is only one of the services that I have used, and it is a big application. The tool has a lot of UI built on Angular, which is then converted as a microservice and clubbed with Java Spring Boot before deploying it on Azure Kubernetes Service (AKS).

The product offers security and access management features, but there are some areas, like encryption, where some improvements can be made. I rate the product an eight out of ten for security and access management features.

The product's integration with the existing CI/CD pipelines is good. I rate the tool's integration with the existing CI/CD pipelines an eight out of ten.

I rate the overall product an eight out of ten.

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.

The solution's logs have room for improvement. I believe that consolidating the logs would help to improve the recall of information from them. With so many logs and such a large amount of data, it would be much easier to obtain relevant information if the logs were merged into a single log.

I would like to have an easier migration from on-prem to the cloud Azure Kubernetes Service. I can complete the task quickly, but I'm not sure many others can accomplish it at the same time or with the same amount of effort, since it may be a bit challenging, to begin with, if we don't have a full understanding of the concepts. Therefore, it would be beneficial if the service provides a resource to make the integration process simpler. 

I believe Azure provides a great service, and I'm working with the solution on a daily basis. However, Azure Kubernetes Service can be improved to make it easier to manage. The user interface can be a bit overwhelming, especially for those who are unfamiliar with the concepts. I suggest having a wizard that simplifies integration and creation of a new Kubernetes in the cloud.

I have been using the solution for almost two years.

The initial setup is straightforward. The deployment takes one and a half days.

We could spend as little as $25 or $30 a month on Kubernetes Services, compared to the typical $100 a month expenditure for a virtual machine.

I give the solution an eight out of ten.

When our clients are informed of the steps and processes involved in deploying Azure Kubernetes Service, they are more confident in taking that step to migrate.

Using Azure Kubernetes Service will save both time and money by decreasing administrative burdens and costs associated with cloud or on-premise hosting.

Could you please describe your customers' usual use cases for Azure Kubernetes Service (AKS)?

Could you please tell what features of Azure Kubernetes Service (AKS) you have found the most valuable?

There might be something that you find indispensable in Azure Kubernetes Service (AKS).

In your experience, how has the integration of Azure Active Directory with Azure Kubernetes Service (AKS) helped enhance the security of application?

Could you please assess the impact of Azure Kubernetes Service (AKS) built-in monitoring and logging features on your ability to track applications performance and troubleshoot issues?

How have the monitoring and logging features impacted the ability to track application performance and troubleshoot issues?

Could you please tell what areas of Azure Kubernetes Service (AKS) you think could be improved or enhanced?

It doesn't necessarily have to be something advanced. Perhaps there are some minor things, such as improving the user interface, making the configuration or customization more flexible. Or maybe there were some limitations that you would prefer to remove?

Would you prefer to improve the flexibility with the network services?

Four or five years now?

Could you please rate how scalable this solution is from 1 to 10, where 10 is the highest scalability?

Specifically about the scalability, does it scale well? Does it need improvements?

Could you please share your impression on the pricing, setup cost and licensing of Azure Kubernetes Service (AKS)?

The costs could be optimized in some way.

Have you been working with Azure Kubernetes Service (AKS)?

Has automatic scaling capability helped your organization, or your customers' organization, to manage varying workloads and ensure high availability?

I am calling from PeerSpot. We are the leading review platform. We collect reviews from real users of enterprise technologies. Currently, we are expanding our database of reviews.

At PeerSpot, we collect reviews for different technical solutions, different categories and vendors including Microsoft, VMware, Oracle, SAP, Amazon, Google, and many others.

If you don't already have an account on PeerSpot, PeerSpot will create an account for you and email you login credentials. PeerSpot will publish your review in written or audio format on peerspot.com and make it available to other users. PeerSpot will email you a link to a written review, and you will be able to edit it at any time. Your review may be made available to third parties and third-party websites, and if you choose to remain anonymous, your name will not appear with the review. You are also opted in to receive email notifications relevant to your review, which you can opt out of at any time. The use of your review is subject to PeerSpot's terms of use that may be accessed at peerspot.com.