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 8.9 out of 10
N/A
Kubernetes is an open-source container cluster manager.
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 …
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 …
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 …
I didn't have too much experience or exposure to OpenShift but I do remember that in certain areas our organization found Kubernetes to be more useful and met our needs in comparison to OpenShift. Although I can't compare, I think it's easier to customize Kubernetes because of …
At one instance, there was a fire in our data center and the backup power had some issues because of which the whole DC went down. I believe with AKS and the replication it's easier to handle such a situation. Also, the scenario would have been pretty transparent to the end-users.
K8s should be avoided - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. Kubernetes is a good choice - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills.
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
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 like Amazon Elastic Kubernetes Service and Google Kubernetes Service, Azure Kubernetes is most cost-efficient with the same facilities and with an advantage to configure easily, manage easily, as it is one click manageable with Microsoft applications. It provides high Microsoft security to containers and secures applications from any kind of harm.
Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.