Microsoft's Azure Kubernetes Service (AKS) is designed to make deploying and managing containerized applications easy. It offers serverless Kubernetes, an integrated continuous integration and continuous delivery (CI/CD) experience, and enterprise-grade security and governance. It allows development and operations teams on a single platform to rapidly build, deliver, and scale applications with confidence.
N/A
Pricing
Azure Kubernetes Service (AKS)
Editions & Modules
No answers on this topic
Offerings
Pricing Offerings
Azure Kubernetes Service (AKS)
Free Trial
No
Free/Freemium Version
No
Premium Consulting/Integration Services
No
Entry-level Setup Fee
No setup fee
Additional Details
—
More Pricing Information
Community Pulse
Azure Kubernetes Service (AKS)
Considered Both Products
Azure Kubernetes Service (AKS)
Verified User
Engineer
Chose Azure Kubernetes Service (AKS)
This depends fully on your needs respectively what you expect or the amount of work you can deal with. Both services are not the silver bullet that will take care of all your pain points. It is needed to analyze/evaluate them carefully and then decide which makes the most …
Amazon EKS stacked up very well and had better performance in some areas. However, Azure Kubernetes Service was a better fit given our Azure environment.
AKS is more powerful than Azure App Service for containers, but it is also very complex. It is great for running large container-based applications and microservices, but you need some Kubernetes knowledge to manage it. When compared to EKS, both AKS & Azure App Service are …
Straight from the beginning, the Github connections are simpler, the permissions and access for users is simpler. Certificate renewal doesn't need to be a worry. There is an option of node-auto provisioning.
Azure Kubernetes Service (AKS) makes you do all of the above with less …
Integration with other standard azure services make Azure Kubernetes Service (AKS) case strong. As we use most of the azure services it is easy to integrate. It is difficult to use EKS as the user interface is not intuitive and difficult to integrate. The services need to be …
Due to cost efficiency. And using AZURE cloud for other services as well. Azure Kubernetes Service is more suitable to configure CI/CD pipelines. With a facility of automated or One click deployment and integration of the application. As compared with other Kubernetes Services …
Worked with very similar in-house-built Kubernetes/container management system. We are leveraging AKS as it's more robust and stable being in the technical space for quite some time. Also, it has got a vast number of management and security features which makes it more …
Director, eCommerce Analytics and Digital Marketing
Chose Azure Kubernetes Service (AKS)
The ability to create new instances (i.e. elastic provisioning) is probably the fastest with Azure Kubernetes Service compared to the alternatives that I have looked at. From a pricing perspective, Microsoft always seems to find a way to be more competitive in this area, and …
[Azure Kubernetes Service (AKS)] is largely similar to EKS. I use both products fairly interchangeably and the decision comes down to which ecosystem you are part of and the which locations are important to you.
AKS works very well for running containerized applications that require high availability and scalability. This includes systems like our HRIS platform and customer-facing web applications. AKS is a good choice when applications are broken into multiple services that need independent scaling and deployment. It provides the flexibility needed to manage these architectures effectively. But for single, low-traffic applications or simple internal tools, AKS can be overkill. For scenarios like that Azure App Service would be better.
As already said, the UI/CLI and even terraform are perfectly fine, but certain details could be documented better. For instance, if I want to secure the whole Azure Kubernetes Service (AKS) with my own managed keys, then it is very complex and hard to get there. Not really a single source that gives you the whole picture. Besides that, it is still good to use, in most cases intuitive but details mentioned as above can be tricky.
Amazon EKS stacked up very well and had better performance in some areas. However, Azure Kubernetes Service was a better fit given our Azure environment.