Azure Kubernetes Service (AKS) Reviews and Ratings

Use Cases and Deployment Scope

The problem that Azure Kubernetes Service (AKS) adresses is the need for an runtime environment that allows to run our application in an orchestrated platform, that like Kubernetes allows automated deploy/management of containerized images. For this purpose it would be possible to use virtual machines (e.g. with plain docker) but of course even with a reduced complexity in some regard, such a solution would offer way less possibilities e.g. the use of an k8s operator. Besides this, Azure for example offers options (data centers, pricing)

Likelihood to Recommend

In a scenario, where a company respectively a team uses a managed K8s for the first time, the Azure Kubernetes Service (AKS) can be overwhelming. So many different options respectively aspects to consider, in my opinion this makes it very hard to start without outside support. In addition, Azure does not offer a terraform runtime as e.g. Terraform Cloud, you need to take such things in account too.

But if you have the need for a lightweight k8s that starts up relatively fast, the Azure Kubernetes Service (AKS) is suited for you.

Use Cases and Deployment Scope

Our main use is that it allows us to run and manage our containerized application in a standardized way. It helps eliminate underlying hardware dependencies and offers us one pane of glass in a very reliable and scalable environment.

Likelihood to Recommend

Azure Kubernetes Service is a good choice if you're already on Azure and need to manage microservices or containerize apps. It works well for our internal apps and APIs and have an easy integration with the rest of the MS ecosystem. For smaller operations / teams, it's probably overkill for what they need.

Use Cases and Deployment Scope

We use Azure AKS to run and manage our HRIS platform, which manages attendance and related tools for company employees. It also hosts several small web applications, both internal and customer-facing. Basically, AKS addresses the need for high availability, scalability, and automated deployments. Overall, it allows our team to focus on delivering features faster while maintaining a stable and scalable application.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

We use Azure Kubernetes Service (AKS) for our service deployments for our backend services. Our services are kubernetes based so this provides a good option for keeping our services deployed as we like.

Likelihood to Recommend

It is good if you are already running kubernetes, the deployments which are running seldom give you issues. However a few things are to be learnt when using it, which are not very obvious and leave room to be desired.

You will have to manage the node pool on your own because there is currently no options of auto-node provisioning like GCP which is a lot less headache.

You need to set up your own certificate renewal

Sometimes the node pool just won't deploy your services and you have to leave resources in a node which is complete wastage.

Use Cases and Deployment Scope

We use Azure Kubernetes Service (AKS) to deploy container workloads mostly for microservices and other applications. It gives us flexibility in terms of scaling the compute based on application requirements. We can easily expand immediately rather thank waiting for someone to actually provision the compute. Also we are using Azure Kubernetes Service (AKS) to do a burst mode where we need some workloads to run for a short amount of time and then shutdown. Azure Kubernetes Service (AKS) perfectly fits into that.

Likelihood to Recommend

It is cheap alternative to Openshift and can easily be scaled in cloud. Almost offers the same features as Openshift but with lesser cost. <div>CI/CD capabilities are lacking </div>

Use Cases and Deployment Scope

Used Azure Kubernetes for CI/CD pipeline for scale and manage microservice application. To manage and containerize applications, scaling services based on load. Used Azure Kubernetes for all application deployment and integration, containerization and scaling of applications. It is highly appreciable with its usage and policies, easy to maintain, governance and helpful for continuous deployment and integration.

Likelihood to Recommend

Azure Kubernetes Service is most cost efficient kubernetes service. it has high security, good governance and easy to manage. Areas where it is less appropriate is manual cluster updates. Azure Kubernetes is most appropriate to use for containerization, continuous deployment and continuous integration. Its very easy to configure and can work with jenkins, and build tools as well. Its easy governance provide facility to manage appropriately. But the major issue is with when configuring clusters and a regular update of policy is required, in this case it requires to create new setup every time rather than updating the same existing items.

Use Cases and Deployment Scope

Azure Kubernetes Service (AKS) helps to offload the data and high processing load (as need be) to outside our data center and increase the availability for different necessary applications. The transition to AKS wasn't that difficult. We are almost confident and ready to have more production data in AKS.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

Azure Kubernetes Service (AKS) is being used primarily to support internal analytics applications that need to scale up and down for a variable user base each day. These internal applications support warehouse operations primarily but we are branching out to other functions such as sales, product development and marketing science.

Likelihood to Recommend

Azure Kubernetes Service is well suited for companies that need to rapidly scale (or remove storage capacity) quickly to support any type of online application. In our case, we built an application for the warehouse team. Around the holidays, when the staff increases quickly, the applications have way more users, requiring more storage.

Use Cases and Deployment Scope

We use [Azure Kubernetes Service (AKS)] to deploy and manage multiple instances of micro service APIs for our customers. [Azure Kubernetes Service (AKS)] allows us to quickly deploy and manage our APIs at scale in a repeatable way.

Likelihood to Recommend

[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.

Use Cases and Deployment Scope

Azure Kubernetes Service is used by the Product development and Cloud team here. It is used to scale the microservices very easily. It provides an open solution that offers portability for both user containers and user application configuration. It also accelerates containerized application development for the developers.

Easy to set up in CI/CD pipeline It has a good pricing option as well in Azure. Basic works fine.

Likelihood to Recommend

Azure Kubernetes service works well, installs easily, is robust and is constantly updated. It uses a great environment when you're running a bunch of servers handling user traffic. The monitoring is quite nice too. Except for the monitoring tools for the database. Azure Kubernetes service still doesn't support autoscaling of nodes. It takes time to fully set up. But once you get going it’s fine.