Kubernetes Reviews

We use this solution to assist with our infrastructure development work.

This solution provides a comprehensive way to scale up our ports and containers, without having to use multiple products.

The solution does not work with third-party tools, or alternative cloud providers, which limits the extent that we can utilize it to.

We would like to see visualization support added to this solution, in order to provide a wider single view of the infrastructure. 

We have been working with this solution for six months.

We have found this solution to be very stable; the only issues that have occurred have been from human error in the configuration.

This solution is extremely scalable, if a business has the budget available to do so.

The technical support for this solution is good, as long as you can provide extensive details on the issue that has arisen.

The initial setup of this product is quite complex, and requires time to understand what is needed to implement it properly. However, once the expertise has been gained, the deployment is quick and straightforward.

The solution was deployed using a third-party consultant.

This solution provides a platform for all development projects, which means that once it is implemented for one project, it can then be used for all future ones. 

The solution itself is open-source, so there is no cost attached to it. However, it requires a virtual machine to operate, which does come at a cost; a choice of a pay as you go model, or a monthly charge via an enterprise agreement. 

There is a pricing calculator available, where organizations can determine the level and number of virtual machines required, and how much that will cost.

It is important to understand the structure of the solution as a system in its own right, and we would recommend that organizations invest in vendor neutral training before implementation begins.

I would rate this solution an eight out of ten.

I use the product for microservices. 

I am impressed with the product's coupling of resources and flexibility. 

The tool needs to improve its UI. The tool is very complex and basic. 

I have been using the solution for six months. 

We haven't encountered any issues with the product. 

I would rate the product's scalability an eight out of ten. 

The solution's setup is difficult and we need to write a lot of commands. It takes one day to complete the setup. We require two people for the solution's deployment and five people for its maintenance. 

I am using the solution's open-source version. 

I would rate the product a seven out of ten. 

We are an IT services company, and I am part of a team of DevOps engineers deploying Kubernetes for customers. We deploy it on a virtual machine, so you can deploy it anywhere. 

The use case depends on the customer's deployment. For example, if the customer has microservices for lots of applications, they can use Kubernetes to segregate new microservices into different segments. They're not using a monolithic application. The same application has different components.

The best feature is autoscaling. It's effortless to use for scaling deployment parts, CI/CD, etc. 

Kubernetes should improve its consistency across different types of deployments. My customers tell me that they get much better performance when Kubernetes is deployed on VM versus PaaS services from Azure. 

I have been using Kubernetes for about two and a half years.

Kubernetes is highly stable. 

The scalability is an excellent aspect of Kubernetes. It can scale up horizontally and vertically. You can scale by cluster and node. Scalabiity is the best part of Kubernetes.

We have never contacted Kubernetes support. If have a problem, we raise a ticket to Microsoft, and their engineers will help us. 

Deploying Kubernetes is straightforward. The total deployment time depends on the number of applications and repositories we have on that day. If you are only setting up Kubernetes, it takes about five to 10 minutes, excluding the front-end IP, etc. 

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. 

I rate Kubernetes eight out of 10. If your team has experience with containerization, they should work on Kubernetes. It will make development and deployment easier. 

I recommend first containerizing your application and running it in a dev environment to test it and get some experience before implementing it in a production environment.

We have several use cases, but our primary use is for microservices.

One of the most valuable features is the thickness of the cloud platform or on-prem file, which makes the solution straightforward to shift and scale. It works well with different types of deployment strategies and networks.

The product features good integrations with other platforms. 

It would be great if Kubernetes could handle a level of data backup.

We have been using the solution for around five years. 

The solution is stable, and I rate it ten out of ten here. 

The platform is scalable, and we have over 30 customers using it. 

Most of our users have a basic knowledge of our definitions and account flows, so the standard practice is to raise issues when we encounter them. Kubernetes technical support can deal well with the kind of problems we face.

The initial deployment was straightforward; we used Kubespray in Ansible, and it took less than an hour.

Kubernetes is free; it's open-source software.

I rate the solution ten out of ten. 

The tool does everything we need, and we believe we have made the best choice.

I'm hesitant to recommend the platform as I prefer people to decide for themselves what is best for them, and I don't want to push a solution if someone doesn't need it. Some users will have issues only Kubernetes can solve, and they should find out how to leverage it.

The most valuable features of Kubernetes are the integration with Docker and there is plenty of documentation available. We work with Docker as a container, and it is more integrated with Docker than VMware Tanzu.

Kubernetes could improve by having better integration with VMware solutions.

I have been using Kubernetes for approximately three years.

Kubernetes is stable. They are the leader in their category.

If the platform for Kubernetes is VMware it is not scalable, but if the platform is Linux, it's scalable.

There are approximately 15 developers and five network administrators using the solution in my organization.

The technical support from Kubernetes is good.

I have used VMware Tanzu previously and I would like to work with it more because it is better integrated with other VMware solutions, such as vCenter, vSphere, vSAN, and NSX.

I have done the initial setup of Kubernetes many times, for me the setup is easy. If I am focused I can complete the full implementation in one or two days.

We have received a return on investment from using Kubernetes.

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 the leader in this category, and are very good. However, if the platform they want to implement is VMware, I would advise using VMware 10.

I rate Kubernetes an eight out of ten.

We use this solution for the hosting of micro-services. Kubernetes helps us to orchestrate all the containers hosting these micro-services.

One of the most valuable features is the ability to manage containers and pods. The solution monitors if applications are live and if issues are picked up, it automatically resolves these. This solution keeps our application in working condition. 

This is an open source solution, which gives the community the opportunity to request specific features which the Kubernetes team then work on and add to the solution.

We would to have additional features related to security within the API, instead of needing to install an add-on. 

I have used this solution for almost four years. 

This is a stable solution. 

This is a scalable solution. We are able to ramp up certain campaigns which this solution manages well. We have 400 to 500 people using this solution. 

This solution took one and a half years to get ready in production. We needed to explore a lot of add-ons in order to deploy into the Kubernetes cluster. 

This is a really useful solution that is particularly useful for organizations using micro-services. This solution is not suitable for use with monolithical applications. Kubernetes works well in an on premises or cloud environment.

The suitability of this solution may vary from company to company.

I would rate this solution an eight out of ten. 

If our project requires a cloud deployment we will use a cloud provider's version of Kubernetes. For example, Azure or AWS Kubernetes Elastic Services. We try to make use of whatever is provided by the cloud providers. 

If the project requires an on-premise solution we use products from various vendors, such as Red Hat or other open-source products that can be downloaded and installed for free.

We are using Kubernetes for container management.

Kubernetes use cases are typically containerized application hosting. This is the basic use case that we do. Another use case can be deploying new application microservices which are loosely coupled and containerized using microservices-based architectures.

We can achieve a reduction of almost 50% to 60% of effort in operations by using Kubernetes.

The most valuable feature is the Zero Touch Operations, which involves a new way of performing operations and support. We do not have to do maintenance, the operations are very simple.

Kubernetes can improve by providing a service offering catalog that can be readily populated in Kubernetes. 

The service catalog, for example, could be a CRM application on Kubernetes or an eCommerce retail application packaged on Kubernetes and to be readily deployable. Instead of somebody trying to figure out all the configurations of hosting this on Kubernetes, if something was readily available, which the developers for these CRM or eCommerce products, they could partner with either AWS, Google, or Azure and make the deployment of such applications readily available on Kubernetes. 

This would allow very little work for a business to go live. The business can quickly straight away and subscribe, launch, and use. It is not difficult for an IT team to be involved to create an application environment to start up. It's would be much easier for businesses to use it directly and start off the applications.

I have been using Kubernetes for approximately three weeks.

The stability of Kubernetes depends on how we have designed it. Our design is stable because I know how to design it and if something goes wrong how to fix it.

The scalability is superb, it is highly scalable.

We have 75,000 employees in our organization that is using this solution.

Technical support is not used very frequently. We use advanced-level support occasionally. It is only in certain circumstances when we have some advanced complexity that we reach out to an expert.

A person with a moderate level of knowledge on Kubernetes, with the help of the community forum, and documentation, most of their problems can be solved.

We do not need any particular company, such as Red Hat, to come in and support the Kubernetes environment, or some other company, such as Ubuntu Canonical to be signed up for a contract to support Kubernetes. It's not required.

The initial setup is straightforward, it was not complex.

The maintenance for Kubernetes is very minimal.

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.

I haven't tried all the advanced features of Kubernetes, but I feel it is meeting most of the requirements of a new design architecture for applications to be hosted. I don't see any particular functionality which is not available for me as of now.

The open-source ecosystem is providing lots of ideas to solve all kinds of problems. The open-source ecosystem of developers, implementers, and integrators is providing lots of ideas. If there is something I may not know, I look up to the community forum and receive answers. There are no issues of finding something, however, Kubernetes by itself has to improve. It is a matter of the implementer to discover ideas to solve the problem. The Kubernetes engine is designed very well.

I would highly recommend this solution to others.

I rate Kubernetes a nine out of ten.

We use Kubernetes to orchestrate the containers for deploying our Docker images to Kubernetes. I'm an Azure DevOps lead.

Kubernetes has some advanced features like auto-scaling and a good self-healing facility. If Kubernetes runs in the form of ports and one of the ports dies, a new one automatically appears. These advanced features help us to deploy our application and makes life easier.

I find the auto-scaling feature very good because rather than manually decreasing the number of nodes, we can define the threshold.

The UI should be improved. It would be helpful if it was more graphical. Kubernetes currently runs perfectly with the Linux environment because it has Docker as a container runtime, and Docker works perfectly with the Linux operating system. It should also be able to run with the MacBook and Windows OS, similar to Linux and it would be helpful if they would include this in the next release. 

I've been using this solution for four years. 

The solution is stable. 

If you're using a cloud service provider there's no problem with scalability. When there's a newer version, we'll upgrade our Kubernetes cluster to the latest version. 

We previously had an on-prem solution using some tools like ClearCase, which is a centralized repository we used to work under. Given that everyone is migrating to cloud, we've done the same, migrating our applications to AWS and Azure Kubernetes.

Although it doesn't take long to deploy, Kubernetes is difficult to set up even if it's the small, mini one-node Kubernetes cluster. For a cloud deployment, it's either Azure or AWS. The cloud service provider will take care of the master node. We currently have a DevOps team of seven people. If we have a big cluster, we can it into multiple clusters, one for the Dev team, one for the QA team, and one for production; each team can work on its cluster and deployment can be done quickly. 

Pricing depends on the cloud service provider. Comparing AWS and Azure, Google Cloud has a much better pricing model, as does Linode. We receive a monthly licensing account.

It's important to learn the architecture of Kubernetes and know what each and every component of Kubernetes does. It makes the deployment easier. Whether or not you choose Kubernetes depends on your use case. If you have a business model that requires minimal changes with fixed requirements then Kubernetes might not be the way to go. If you're constantly needing to make changes, Kubernetes is a great solution. 

I rate the solution eight out of 10.