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
Kubernetes
Score 9.3 out of 10
N/A
Kubernetes is an open-source container cluster manager.
N/A
Pricing
Azure Kubernetes Service (AKS)
Kubernetes
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Azure Kubernetes Service (AKS)
Kubernetes
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Azure Kubernetes Service (AKS)
Kubernetes
Features
Azure Kubernetes Service (AKS)
Kubernetes
Container Management
Comparison of Container Management features of Product A and Product B
[Azure Kubernetes Service (AKS)] is great when you need to be able to deploy a large number of services in a highly repeatable way. Once you know how to use it, it is a very fast to stand up a new environment. However there is a lot you need to know to get to that point and it is a specialized area. This is not suitable for small teams who are supporting multiple product stacks.
Along with all the best features and support by k8s, the automatic container scheduling to worker nodes and also self-healing containers which is what I like the most. On the other side, when I was installing the k8s cluster on CentOS 8, it was quite difficult for me, but never mind it is working as we expected and it is a one-time effort. Especially, in my case, there are more than 7 application containers required to run and communicate with each other, so for us, Kubernetes is an optimal solution.
Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.
The Kubernetes is going to be highly likely renewed as the technologies that will be placed on top of it are long term as of planning. There shouldn't be any last minute changes in the adoption and I do not anticipate sudden change of the core underlying technology. It is just that the slow process of technology adoption that makes it hard to switch to something else.
Barring certain missing features such as operator management , open cluster management, it does gives lot of options to host containerized applications. The GUI may be improved and can give user more insights to the cluster rather than using command line tools. The integration with standard azure monitoring tools is a big plus to use Azure Kubernetes Service (AKS)
It is an eminently usable platform. However, its popularity is overshadowed by its complexity. To properly leverage the capabilities and possibilities of Kubernetes as a platform, you need to have excellent understanding of your use case, even better understanding of whether you even need Kubernetes, and if yes - be ready to invest in good engineering support for the platform itself
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 attractive. They even have a model where the cost can be reduced by up to 90% if the application can afford to handle a quick downtime once in a while.
As I said earlier also - - K8s manage the workloads better as compared to OpenStack in terms of reliability, observability & reachability. - K8s is not limited to only a single networking or storage solution as compared to OpenStack. - Networking (which is a key concept) is much simpler in K8s as compared to OpenStack. - It is possible to upgrade your applications without downtime in K8s but in OpenStack, you either have to divert the traffic or face an outage because you have to delete the whole stack & then recreate it.
