Sinior Cloud Architect at a consultancy with 10,001+ employees
Real User
Top 5
May 7, 2024
I would rate the pricing a six out of ten, with ten being expensive. It's a bit costlier for smaller organizations. It's good for bigger organizations, but for smaller organizations or a few workloads, it may be too heavy, not easy to deploy, and the ROI may be less because it requires a control plane, worker nodes, and multiple VMs to run. It's good for bigger organizations where many applications are run, but overkill for handling one or two small applications.
The pricing depends on the project. Ultimately, it's a business decision, and they need to assess the risks and potential consequences. If the benefits outweigh the costs, then it's a worthwhile investment. I'd estimate that it requires more than 10 to 15 percent upfront effort.
Pricing isn't a major concern for us. Since we resell Kubernetes services and focus on providing support, integration, and education, we don't usually have pricing issues. Our customers are more concerned with getting the right support and services than the cost. So, the value we provide is more important than the actual pricing. Pricing might change in the future, but it’s not a big issue for us right now.
It's expensive if it's not correctly configured. Moreover, AKS is just one resource. We have to think about other resources, like Azure key vault, PostgreSQL, or BizTalk, for example. We have to integrate those. But for the AKS itself, it's relatively cheap as long as it's properly configured. I'd rate the pricing a five out of ten. There are additional costs for some things in Kubernetes. For example, if you want to integrate your AKS with Azure monitoring, like analytics, that will spike your costs. It's not just the AKS itself. We have to be careful when selecting solutions. That's why, in our organization, we look for alternatives like Splunk or AppDynamics. But if you're going to use only the AKS, it's cheaper if you configure it correctly.
Kubernetes Consultant, Cloud Architect at a computer software company with 51-200 employees
Real User
Nov 29, 2022
Kubernetes is open source and is an orchestration platform. It is a cost effective solution and its pricing depends on your company and how you use it.
Solutions Architect at Rapyder Cloud Solutions Pvt Ltd
Real User
Sep 8, 2022
Kubernetes is an open-source tool, so you only need to pay for your infrastructure. If you have your own data center, you can install Kubernetes and containerize the server, but if you're using PaaS services from Azure, so you must pay Azure for your utilizing their services. The total cost of ownership depends on your configuration.
Senior network virtualization & storage specialist at Sipand Samaneh
Real User
Jul 29, 2022
The price of Kubernetes could be lower. However, it is less expensive than VMware Tanzu. Additionally, technical support is expensive. The overall cost of the solution is approximately $1,000 annually.
Kubernetes is an open-source solution that can be free. We have some distribution with licenses, such OpenShift and Tucows in Amazon. They are billing services.
Practice Director, Global Infrastructure Services at a computer software company with 10,001+ employees
Real User
Jan 19, 2022
You need to pay for a license if you buy branded products. For example, if you take the services from Azure, AWS, or Google, the price of the Kubernetes cluster is inclusive of the service that's being offered to us on a pay-and-use model.
Learning Manager at a educational organization with 11-50 employees
Real User
Oct 26, 2021
Even though the solution is open-source, one major service we need to pay for is storage. Normally we are using the storage from EMC or NetApps or IBM. These companies created their own stack of provisions and if I want to use their storage for my Kubernetes clusters, these are the license stacks that I need to purchase. Storage is the major component, as the licensing is based on that. Technically, there's an operating system license, which is something that I need to pay by default for every node, that I'm using. Other than that, with any other framework now, OPPA is completely free. Calico is completely free. A lot of frameworks are available. A framework is going to make sure that our entire Kubernetes cluster is based on compliance and is compliance-specific. Whichever customer I'm handling, I always look for ways to save them money because at end of the day, as they're investing in a lot of operational costs. I try to seek out mostly open-source products which are stable and reliable. Still, even if I do that, storage is an area where people need to pay the money.
Multi-Cloud Consulting at a construction company with 5,001-10,000 employees
Real User
Jan 30, 2021
There are different types of licenses. You have a subscription-based license if you are talking about cloud. This has both yearly or monthly available. Or you can go on number of workloads, based on how much workload you're putting on the cloud.
It's open-source and free, so pricing should not be applied here. Google Kubernetes Engine is free in the simplest setup, AWS Kubernetes Engine costs about $50 (depending on the region), in a three master setup, so it's almost the same as the cost of the EC2 instances and it's totally fine from my point of view.
Senior Software Developer at a tech vendor with 51-200 employees
Real User
Oct 22, 2020
The solution can be more expensive for smaller companies. If you run it on a smaller scale it's pricey. However, if you scale up or use it on a larger scale, it's pretty competitive in the pricing. For example, on Amazon, the billing is mostly for the machines that you're using. If you have a lot of containers, hundreds of containers, running on the ECS, it can even be more expensive than if you were running the same containers on some deployment as you're paying for the nodes that are running the machines. If you can use fewer containers in the same machine it can be cheaper. It really depends on deployment. If you decide to take the managed service, be aware that it's $100-$200 extra monthly. It's not much, and it's worth the cost.
The management layer is free, which is perfect. You don't need to pay money for the management layer, but in AWS develop service, you need to pay. I think it is €75 per month for the management layer. It is free here, so you can have as many Kubernetes clusters as you need. You are paying just for the workload, that is, for the machine, CPU, memory, and everything.
The solution is open-source. There are no licensing fees to speak of. It's under an Apache license, so anybody can use it. Some products that go on top of it, however, are licensed.
Kubernetes (K8s) is an open-source system for automating deployment, scaling, and management of containerized applications.
It groups containers that make up an application into logical units for easy management and discovery. Kubernetes builds upon 15 years of experience of running production workloads at Google, combined with best-of-breed ideas and practices from the community.
I have had a good experience with pricing, but the setup costs are high.
Since we use Kubernetes on-premises, the costs are related to our expertise and the personnel we hire.
I would rate the pricing a six out of ten, with ten being expensive. It's a bit costlier for smaller organizations. It's good for bigger organizations, but for smaller organizations or a few workloads, it may be too heavy, not easy to deploy, and the ROI may be less because it requires a control plane, worker nodes, and multiple VMs to run. It's good for bigger organizations where many applications are run, but overkill for handling one or two small applications.
The pricing depends on the project. Ultimately, it's a business decision, and they need to assess the risks and potential consequences. If the benefits outweigh the costs, then it's a worthwhile investment. I'd estimate that it requires more than 10 to 15 percent upfront effort.
Pricing isn't a major concern for us. Since we resell Kubernetes services and focus on providing support, integration, and education, we don't usually have pricing issues. Our customers are more concerned with getting the right support and services than the cost. So, the value we provide is more important than the actual pricing. Pricing might change in the future, but it’s not a big issue for us right now.
Microsoft provides reasonable costs for Kubernetes.
It's expensive if it's not correctly configured. Moreover, AKS is just one resource. We have to think about other resources, like Azure key vault, PostgreSQL, or BizTalk, for example. We have to integrate those. But for the AKS itself, it's relatively cheap as long as it's properly configured. I'd rate the pricing a five out of ten. There are additional costs for some things in Kubernetes. For example, if you want to integrate your AKS with Azure monitoring, like analytics, that will spike your costs. It's not just the AKS itself. We have to be careful when selecting solutions. That's why, in our organization, we look for alternatives like Splunk or AppDynamics. But if you're going to use only the AKS, it's cheaper if you configure it correctly.
I am using the solution's open-source version.
It's free and open-source; anyone can use it. So there are no hidden fees or anything regarding Kubernetes.
We use the solution's open-source version.
Kubernetes is free; it's open-source software.
This is an open-source solution, so there are no licensing costs associated with its use.
Kubernetes is open source and is an orchestration platform. It is a cost effective solution and its pricing depends on your company and how you use it.
Kubernetes is open-source. It's free, but we're charged for AWS utilization.
Kubernetes is open source.
The solution is open source and has no fees.
Kubernetes is an open-source tool, so you only need to pay for your infrastructure. If you have your own data center, you can install Kubernetes and containerize the server, but if you're using PaaS services from Azure, so you must pay Azure for your utilizing their services. The total cost of ownership depends on your configuration.
The price of Kubernetes could be lower. However, it is less expensive than VMware Tanzu. Additionally, technical support is expensive. The overall cost of the solution is approximately $1,000 annually.
Kubernetes is an open-source solution that can be free. We have some distribution with licenses, such OpenShift and Tucows in Amazon. They are billing services.
I don't deal with the pricing aspect of the solution.
We pay a monthly fee in order to sue the solution.
You need to pay for a license if you buy branded products. For example, if you take the services from Azure, AWS, or Google, the price of the Kubernetes cluster is inclusive of the service that's being offered to us on a pay-and-use model.
You don't need a license for Kubernetes, but you do have to pay for usage.
Even though the solution is open-source, one major service we need to pay for is storage. Normally we are using the storage from EMC or NetApps or IBM. These companies created their own stack of provisions and if I want to use their storage for my Kubernetes clusters, these are the license stacks that I need to purchase. Storage is the major component, as the licensing is based on that. Technically, there's an operating system license, which is something that I need to pay by default for every node, that I'm using. Other than that, with any other framework now, OPPA is completely free. Calico is completely free. A lot of frameworks are available. A framework is going to make sure that our entire Kubernetes cluster is based on compliance and is compliance-specific. Whichever customer I'm handling, I always look for ways to save them money because at end of the day, as they're investing in a lot of operational costs. I try to seek out mostly open-source products which are stable and reliable. Still, even if I do that, storage is an area where people need to pay the money.
The solution requires a license to use it.
Licenses for Kubernetes are on a yearly basis.
We'd like the pricing to be lower than what it is now. We pay a yearly licensing fee.
There is no licensing fee. The solution involves the use of an open source tool.
There are no licensing fees.
The solution is affordable.
Kubernetes is open-source.
Kubernetes is an open source solution so there is no cost and, for now, no additional costs but we pay for the platform.
There are different types of licenses. You have a subscription-based license if you are talking about cloud. This has both yearly or monthly available. Or you can go on number of workloads, based on how much workload you're putting on the cloud.
It's open-source and free, so pricing should not be applied here. Google Kubernetes Engine is free in the simplest setup, AWS Kubernetes Engine costs about $50 (depending on the region), in a three master setup, so it's almost the same as the cost of the EC2 instances and it's totally fine from my point of view.
The solution can be more expensive for smaller companies. If you run it on a smaller scale it's pricey. However, if you scale up or use it on a larger scale, it's pretty competitive in the pricing. For example, on Amazon, the billing is mostly for the machines that you're using. If you have a lot of containers, hundreds of containers, running on the ECS, it can even be more expensive than if you were running the same containers on some deployment as you're paying for the nodes that are running the machines. If you can use fewer containers in the same machine it can be cheaper. It really depends on deployment. If you decide to take the managed service, be aware that it's $100-$200 extra monthly. It's not much, and it's worth the cost.
The management layer is free, which is perfect. You don't need to pay money for the management layer, but in AWS develop service, you need to pay. I think it is €75 per month for the management layer. It is free here, so you can have as many Kubernetes clusters as you need. You are paying just for the workload, that is, for the machine, CPU, memory, and everything.
The solution is open-source. There are no licensing fees to speak of. It's under an Apache license, so anybody can use it. Some products that go on top of it, however, are licensed.