Kubernetes Reviews

The primary use case of the solution is container orchestration for a microservices-based architecture.

I worked on deployment in the cloud and on-premises.

The solution has improved our organization by providing a computing layer abstraction between the cloud provider and on-premise. This has given us higher consistency in management and deployment strategies. The solution also reduces the effect of discrepancies between development and production environments.

The most valuable feature of the platform is the auto-healing and auto-scaling ability to offload to the platform tasks that were previously managed by humans.

There is a large ecosystem of products surrounding Kubernetes, making it difficult to identify the right solution due to the vast number of options.

I have been using the solution for six years.

The solution is a stable mature platform.

Scaling is a straightforward and standard process. With the integration provided by the cloud provider, we can even enable automatic scalability.

Setting up without Kubernetes provider services is complex.

I give the solution a nine out of ten.

There is a large amount of overhead associated with maintenance, as we have to maintain everything from the operating system to the application. The cycle of updates and patches for the platform itself is very frequent, with a new version released every four months and various security patches in between. This makes the maintenance task very large if we have to do it ourselves.

The main benefit of Kubernetes is that it is currently the standard for container orchestration. Kubernetes is available across different cloud providers, providing consistency in management and portability that is not available with other products.

In the beginning, the solution may feel as if it has a lot of moving parts that are confusing and overwhelming.

Kubernetes is open source. It's an orchestration platform for container clusters.

The solution can be deployed anywhere, such as on-premise or in the cloud.

Kubernetes is a leading container orchestration solution, known for its simplicity and ease of use. Being open-source, it benefits from large community support, including enterprise support. Many companies offer their own version of Kubernetes, making it widely adopted and supported in the industry.

The lack of native support for billing and self-service capabilities is an area Kubernetes could improve. This requires the use of third-party integrations or managed services in order for customers to be able to deploy clusters on their own. It would be beneficial to have these features built-in into the Kubernetes platform.

I have been using Kubernetes for approximately one year.

This is one of the most stable platforms in the market.

I rate the stability of Kubernetes a nine out of ten.

The scalability of Kubernetes is excellent. You can have one to two nodes and it can scale to 1,000,000 nodes.

I rate the scalability of Kubernetes a ten out of ten.

The initial setup for Kubernetes is not straightforward. Setting up a Kubernetes cluster requires some level of experience and training, as well as knowledge. The procedures and setups vary depending on the specific deployment scenario.

I rate the initial setup of Kubernetes a six out of ten.

We use one person to deploy the solution. However, it can depend on if it's a bare metal setup for on-premise, this could take longer. Starting from the bare metal for a cloud deployment one person is enough.

For the maintenance of Kubernetes, one person is more than enough because it's an orchestration platform. They only manage the container or microservices.

My advice to others is for them to gain a basic understanding and training in Kubernetes and also develop some management skills. If they are willing to learn and can manage the technology, Kubernetes is a good choice as it is an emerging and leading technology in the cloud industry.

I rate Kubernetes a nine out of ten.

This solution is used for serving DevOps.

Kubernetes is quite controversial. It increases developers' overhead and allows them to provide trolling updates and zero downtime. In addition, it has increased the possibility of delivery of new features without training downtime of the application.

All the current features are quite harmonic, and they require each other.

We have been using this solution for about two years, and it is deployed on the public cloud.

I rate the scalability a ten out of ten. It is infinitely scalable, and no feature can scale like Kubernetes. How much we use the solution depends on the company's business needs.

We did not use other solutions and have only used Kubernetes.

I rate the initial setup a four out of ten. It requires call writing come, YAML files and help to chart things done. You need to add something new to improve the solution and handle the traffic. The deployment was completed in-house, and one person was enough to complete the deployment.

We have not seen a return on investments. It's saved the possibility of rollout and zero downtime from projects. It's like the biggest advantage of the human ordinate.

It is an open-source solution, so it is free to use. People on the internet always advocate for cheaper options. If you want to use a managed solution, you'll have to pay for it, and it can be expensive if you manage it on your own.

I rate this solution an eight out of ten. Regarding advice, if you have a small infrastructure, do not go with full Kubernetes. Instead, use smaller solutions like K3s or Rancher and full Kubernetes if you have a vast infrastructure.

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. 

This is a container orchestration platform used to organize our containers. Most of our applications are developed containers. We need Kubernetes to manage the network and volumes. We had approximately 50 tech team members using this solution. 

This solution is cost effective and fast. We are able to use Kubernetes to orchestrate hundreds of container images which has been a major benefit. 

There is a feature called Terraform and, based on the reviews I have read, it could be improved. 

I have been using this solution for two years. 

This is a stable solution. 

You can scale Kubernetes up and down easily.

When it comes to support, we have mostly used the documentation provided for the solution. 

The initial setup is straightforward but you do need to know the basics. The speed and ease of the set up depends on how fast you want the application to be and the amount of traffic your application generates.

When I first started using Kubernetes, it was quite challenging. I would rate the set up a two and a half out of five.

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.

We evaluated solutions like OpenShift and Rancher. The great thing about Openshift is that it is ready to use out of the box. When using Kubernetes, you have to set everything up on your own. Besides that, there are not many differences between Kubernetes and the other solutions. 

This is a very good registration platform. It saves costs and is fast. You can deploy thousands of replicas of your application all at once, as long as you have enough resources. 

I would rate this solution a nine out of ten. 

We are using the solution to deploy applications that are based on the microservices architecture.

The solution has many valuable features but the most impressive is the ability to scale an application and continuously monitor if all the components of the application are functioning correctly. If one part fails, it will recreate that component only, without disrupting the application. Another valuable feature, unlike other solutions that use the imperative way of programming this solution uses the declarative way, so you only need to describe the end result and it will do everything to arrive at that state.

The solution can be improved by adding a management console that will allow the use of a graphical interface to do what is usually done using command line instructions. I would like to have a simplification of the update process, which is currently not straightforward and time-consuming. The security of the solution is in its infancy and needs a lot of work.

I have been using the solution for over a year.

The solution is stable as long as you don't touch the configuration and you know what you are doing otherwise, it will crash easily.

The solution is scalable, but it is difficult to do as a standalone solution. Most organizations use paid solutions, such as Rancher, or OpenShift that are similar to operating systems that embedded the solution in them.

The initial setup is straightforward. I am able to have a fully working cluster within half an hour. There are tools available that can help automate the deployment and reduce the time to under 15 minutes.

The implementation was completed in-house.

The solution is open source and has no fees.

I give the solution eight out of ten.

I suggest anyone who would like to use this solution first get the certification. You must be knowledgeable with Linux and comfortable with the command line interface.

We have many applications that are running on top of Kubernetes.

The most valuable feature of Kubernetes is container orchestration.

Kubernetes can improve pod escalation.

In a future release, the dashboards could be more detailed. They are too simple.

I have been using Kubernetes for approximately five years.

Kubernetes is stable.

We have approximately 100 people using Kubernetes.

I have used the support from Kubernetes and it was good.

There is a license to use Kubernetes.

My company chose Kubernetes because it is the best tool for orchestration containers.

My advice to others that want to use this solution they should first study container concepts and create a POC.

I rate Kubernetes a nine out of ten.

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.

Kubernetes is used to Dockerize and containerized applications.

Kubernetes has helped our organization by making our time-to-market better and the continuous integration and development are good. We can develop DevOps and FinOps methods.

The most valuable feature of Kubernetes is the integration with other solutions, such as Formative and Grafana.

Kubernetes could improve security. The security is really hard to deploy with proxies and other elements. Additionally, We have had some issues downloading repos and libraries.

In the next release, Kubernetes should develop a good interface for the administration and make the deployment of the solution easier.

I have been using Kubernetes for approximately six months.

Kubernetes is highly stable.

The scalability of Kubernetes is very good.

We have approximately 1,500 people using the solution in my organization. We have IT managers, administrators, and developers use it.

The support we have received has been very helpful.

I rate the support from Kubernetes a five out of five.

We have used other solutions previously, such as One Automation, and Nokia for traffic management.

The deployment of Kubernetes could be better. The initial setup took approximately a week to complete.

I rate the initial setup of Kubernetes a four out of five.

For our implementation strategy, we enabled a cluster in the production environment, dev environment, and pre-production environment and we made two masters and many nodes. However, it depends on the application and the traffic volume.

We use integrators for some of our deployments and for others we use only our team.

We use four of five administrators for the maintenance of the solution.

We have seen an ROI because the time it takes to market has been very quick to make a deployment.

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.

If you need to take care of proxies and configuration you may find the use of the GitHub repo Cube install helpful. It can help deploy and administrator the Kubernetes platform.

I rate Kubernetes an eight out of ten.

Kubernetes is a container management platform, and all our microservices are deployed on this platform.

There are features that come out of the box with Kubernetes, with respect to scaling, reliability, etc. It's the leading container management platform. There are other competing ones, but this is the leading one.

It has multiple instances of the application running. If one of them goes down, the other one automatically spins up.

It would be nice if they could make it easier for developers and infrastructure staff to automate some of the pieces that they have to do manually at the moment.

This is a solution I've been using for four or five years.

It's stable. It's managed by the cloud provider.

Depending on the SLAs with respect to scalability, we can scale up and down as per our demand. We could increase the number of nodes instantaneously for our requirements. In our company, we have 5,000 people around the world using Kubernetes.

As for initial setup, If it is on an on-premises environment then it's a little bit tricky, but if it's on public cloud, then they have an offering where you can spin up clusters within minutes. Those are managed by the cloud providers. On cloud platforms, the initial setup is easy, but if you want to spin up your own cluster and manage that, then it could be a lot of work. Spinning up might be easy, but maintaining that cluster could be a lot of work.

Look at your use cases to make sure that Kubernetes is required. It is generally required when there are concerns with scalability or when there is a need for a solution that is highly available and highly scalable. If this is the case, then it makes sense to use Kubernetes.

It could be used as a global tool as well. Some of the nodes would be on-premises and on the cloud or multi-cloud.

However, if you have a simple application which is used by your own company and some internal applications, and is not used by many people, and scalability is not the concern, then you shouldn't go for Kubernetes.

I would rate this solution at eight on a scale from one to ten.