TrustRadius Insights for Azure Kubernetes Service (AKS) are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Simplified Data Replication: Users have appreciated how AKS simplifies the process of replicating data to multiple regions, making resource management across the organization easier. This streamlined approach saves time and effort for users when handling data distribution tasks.
Beneficial Development Features: Reviewers find the continuous deployment, continuous integration, and containerization features beneficial for their application development processes. These functionalities enhance workflow and support application updates.
Scalability and Flexibility: Users highlight the scalability of AKS, noting that it quickly scales based on user demand, providing flexibility as needed. Additionally, they praise the highly repeatable process offered by AKS for easy scaling of resources to meet varying demands effectively.
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.
Pros
Container workloads
Auto scaling
Standard kubernetes deployment
Easily integrate with Azure monitoring and Logging
Cons
GUI on azure portal need to enhanced.
The feature set should be matching with Openshift which is also kubernetes based
Troubleshooting errors
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.
CI/CD capabilities are lacking
VU
Verified User
Manager in Information Technology (201-500 employees)
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.
Pros
Continuous deployment
Continuous Integration
Containerization of application
Security of Microsoft playing a vital role
Management and governance of application
Cons
Need to update cluster manually
Policies cannot be updated for existing components
if any change in policy every has to create cluster
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.
VU
Verified User
Team Lead in Information Technology (501-1000 employees)
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.
Pros
AKS makes it easier to replicate data to multiple regions
Azure portal make it easier to manage the resources of the organization
Cons
It's a little challenging to foresee how much would be the cost to incur for our usage
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.
VU
Verified User
Administrator in Information Technology (1001-5000 employees)
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.
Pros
Scales quickly when the user base increases randomly
Downgrades very fast if a bunch of users hop off the system
Great dev UX for IT
Cons
The pricing structure is complicated
The stats on usage isn't the easiest to understand
The overall microsoft contract is hard to wrap my head around
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.
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.
Pros
Highly repeatable process
Minimizes the amount of software to install
Easily scale resources to meet demand
Cons
Steep learning curve
Expected charges are unclear until you see real production usage
Operations teams need to learn an entirely new skill set
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.
VU
Verified User
Manager in Information Technology (51-200 employees)
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.
Pros
To scale the microservices very easily.
Easy to set up in CI/CD pipeline.
It has a good pricing option as well in Azure. Basic works fine.
Accelerates containerized application development for the developers.
Cons
Database services monitoring is weak.
It doesn't possess a good monitoring solution.
Response times in cloud applications could be faster.
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.