Kubernetes Reviews

Our use case of this product is for mobile banking applications. I'm the executive vice president of the company and we are customers of Kubernetes. 

The scanning and support network are the best features of this product. 

I think Kubernetes should simplify the setup and operation of the product. For now, we don't use many of the features that the solution provides, so there's nothing additional I'd like to see. 

I've been using this solution for over a year. 

Most of the time the product is stable but we do encounter some problems from time to time and it can be difficult to file reports. 

It's quite easy to scale most of the time but sometimes we encounter some difficulties. 

We have contacted technical support but sometimes we connect to online support because the official support is not enough. 

The initial setup is a bit complex and could be simplified. I think it's a simple setup for developers, but maintenance by the system engineer is quite complex, particularly when it comes to locating the problem. We get some support from the system vendor. Once deployed, maintenance is required on both the application and the infrastructure and our IT team is responsible for that. We have around 50 people involved on the system engineering side, they deal with Kubernetes but also with the operating system and database software. We have around 40 users on a daily basis. 

Kubernetes is an open source solution so there is no cost and, for now, no additional costs but we pay for the platform. 

I would definitely recommend this product. 

I rate this solution a nine out of 10. 

We primarily use the solution for orchestration.

Most of the clients we work with are enjoying the DevOps aspects of Kubernetes. They want to be able to safely and quickly deploy new applications. Others just enjoy the modern way they can deploy containers without being a DevOp company. 

The most valuable aspect of the solution is the scalability.

Kubernetes is quite complex. That's the reason there are some companies that are developing tools simplifying the life of the administrator. There are Kubernetes distributions, like Rancher. Rancher is one of my favorites. There are others too, like OpenShift, for example.

I would love to see a feature like VMware's vMotion, meaning a workload can be transferred from one host to another without being restarted. While true cloud native applications typically don't need such a feature, there is still a lot of single-container legacy applications out in the field. These applications get unavailable while being rescheduled to another node, for example when doing node maintenance.

I'd been dealing with the solution for the past three or four years.

The solution if very, very stable. It's a very mature product. While there is no software without bugs, it has 20 or more years of development behind it that makes it very robust.

The solution is extremely scalable. It's one of its greatest selling points. It also works for businesses of any size, from small to large.

Technical support is something I handle myself. I don't need to reach out to the Kubernetes team in order to troubleshoot issues.

We do have manufacturers of specific products that also have their own support we can access if we need to.

I have some experience with Docker. I also have a lot of VMware virtualization experience, although that doesn't have much to do with containers, per se.

That said, almost every software provider tries to adapt their solution to Kubernetes due to the fact that Kubernetes is gaining a lot of attention from everywhere. It's going to be the preferred way to deploy applications.

The complexity of the solution depends on the size of the installation and the product you choose. If you choose Kubernetes without any other tools, like Rancher or OpenShift, it's going to be very difficult and complex. However, if you have the chance to use one of those, it's much easier.

Once the solution is up and running, it requires monitoring, software updates, replacement when something fails, etc. Most of the time it's the provider that manages the infrastructure.

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. 

I am a consultant, and I am just providing information about how to use this kind of software within specific companies.

Kubernetes is evolving now. 1.18 is the latest version, however, we don't have the newest version everywhere. That's the one we choose for new installs when we do them.

When it's deployed on the cloud, some of my customers are using public clouds such as Amazon, Google, or Microsoft. There are also some customers that use private clouds here in Switzerland. I work together with them.

If people are using modern technologies like containers or developing software by themselves, I would recommend this solution.

I'd rate the solution eight out of ten.

If you have a lot of nodes and you want to be able to change the node that you are using, you can use Kubernetes. Kubernetes services allow users to be able to run multiple designs as well.

The stability of the solution is very reliable. The performance is good.

The implementation, and the way that they can, with a few clicks, load hundreds of machines without any trouble is very useful. We found the initial setup to be very straightforward.

There are a lot of benefits.

At this time, there is nothing that I would want to be added to a future release.

The pricing could be improved. It would be ideal if it was a bit less.

I've been using the solution for three years. 

The stability of the solution is very good and the performance is excellent. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

We have about 200 people on the solution at this time.

I'm not using Kubernetes support. I am using Amazon support. I can't speak to how helpful or responsive Kubernetes support would be having no experience with them.

We did not previously use a different solution. We have only ever used Kubernetes. 

The initial setup is very straightforward. It's not overly complex.

The deployment itself took a few weeks. 

We have seven engineers and they're all going to be able to handle Kubernetes.

We handled the installation with the assistance of an integrator. We did not handle the process alone. 

We'd like the pricing to be lower than what it is now.

We pay a yearly licensing fee. 

I'd rate the solution at an eight out of ten. We've been very happy with its capabilities so far.

I would recommend the solution to other users.

We use the latest version. 

We use the solution for deployment purposes.

The solution is easy to use.

The solution could be more stable. 

I have been using Kubernetes for about two years.

The solution is stable, although it could be more so. 

The solution is scalable. 

When it comes to technical support, overall, we have managed with the community.

For this project, we started out with Kubernetes. We started only two years back.

The solution was easy to install, although I was not involved in the process and cannot comment on how long it took. 

There are around five people involved in the deployment and maintenance, consisting of workers and engineers.

There is no licensing fee. The solution involves the use of an open source tool.

There are around 300 people using the solution in my organization.

I would recommend this solution to others. 

I rate Kubernetes as a nine out of ten.

We use this solution to orchestrate our applications.

If for example, you want to use a Microservice for replication, you host it on Docker then you will need to orchestrate your application. This might include autoscaling, security, and traceability for the user.

I like the replication center and the configuration.

The dashboard, monitoring, and login need improvements.

I have been using Kubernetes for five years.

We are using versions 1.15 and 1.20.

Kubernetes is stable.

It's a scalable solution.

This solution is being used in large organizations from the financial sector.

We have not contacted technical support.

I have some experience with OpenShift and Azure.

The initial setup was straightforward.

It can be deployed in 45 minutes to one hour.

There are several teams required for different areas that communicate with each other such as security teams, work teams, and maintenance teams. There are anywhere from five to nine people that we communicate with, who are engineers from each division.

I completed the installation and implementation myself. I did not use the help of an integrator or consultant.

There are no licensing fees.

I would recommend this solution to others.

I would rate Kubernetes an eight out of ten.

We are not using the Google version, but the open source Kubernetes.

This product can be deployed both on cloud or on-premises.

Our use case is mostly for multi-services or the applications which you will try to modernize. Investors will come from monolithic applications to mostly cloud-native applications. When I say cloud-native applications, that means each service component will be part of one container. You need a container orchestration or a management platform. So Kubernetes is actually a management or an orchestration platform for containers. Basically, it works with microservice applications.

One of Kubernetes' top features is its agility, it is very fast. You can deploy a container pretty quickly compared to a virtual machine. That is one strong feature. A second feature is its flexibility because you can use it on any platform. You can use it on Google or AWS or Microsoft or IBM or any clouds. So flexibility of deployment and agility are the top features. It also helps in your maintenance cycles when you do maintenance on your environment.

For improvements, I would say it's actually still evolving so they are already making a lot of improvements along the way. Each and every release comes with new features so I think they're doing well.

One feature I would actually like to see is the network monitoring part. When we talk about communities, it's mostly the computer side. But it does have some enhancements on the networking side which they have recently released. I would like to see more enhancement where we can monitor the networks of the Kubernetes cluster or the Kubernetes workloads.

This Kubernetes product is new so I would say I have been using it around two years.

I am using version 1.18, not the latest one.

Stability is still a question because it depends upon which flavor you're installing. It could be on-prem or it could be cloud, it could be open source. It's still debatable.

That said, stability-wise I haven't seen any problem myself up to now, but I might not be right. There are many other people who are deploying this in a production environment. I haven't done it myself in production so I would not be the correct person to answer that. But for me, I haven't found any stability issues.

Kubernetes definitely has good scalability. 

The number of users on it can vary. It can be used by very small organizations to very large and complex organizations. There is a customer I was working with who has more than 80,000 employees around the globe. But not everyone is a user of this technology. If you're asking about the users of this technology, I would say around 1,000 - 5,000.

Their technical support depends upon which flavor you're installing. Mostly, if you're going to the cloud version, support is definitely provided by the vendors. Like Microsoft provides its own support, AWS provides their own, and even IBM does the same. But if you're deploying on your own prem, that's where the question is. It depends. It's not a product sold by a single company, it's an open source, so big companies like J.P Morgan or Citibank have it deployed on their own premises and support will be their internal teams who will be working on that.

Installation is not a straightforward thing. It's a process that you have to follow step by step. On-prem is a little tedious because you have to spend some time to get this installed and create a platform. But people are mostly inclined towards cloud. They use Kubernetes on the cloud.

I did install it myself in my lab and the install itself doesn't take much time, about a couple of hours. But to go through the documentation takes time. You have to understand each and every component and then try to install that. So it's a combination of both understanding the documentation and then installing. Because it's a new technology, it does take a little bit of time.

It depends. If you talk to a customer and you get a project with them that they want to deploy, you're going to need a project manager or a technical architect, and then you'll need at least one or two guys who can do the hands on deployment. It's not a fairly large team, but you will need a project manager, a technical architect and an engineer.

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.

I would definitely recommend Kubernetes for others who want to start using it.

I would say it is no longer in its inception phase, but it is still in the early phase. The product hasn't matured enough. There are customers who are looking to take this maybe around two years down the line. On a scale of one to ten, I would give Kubernetes an eight.

We use the solution to modernize our IT landscape. We use infrastructure and platform surfaces for our data center. More recently we have added a container as a surface, which is this solution.

The easy deployment of containers is one of the main features I have found useful. In large scale developments, it is less hassle working with containers than virtual machines. It is easier to manage these containers instead of virtual machines, although there is a steep learning curve to graps the benefits of it.

This solution is not very easy to use. We are looking also for some tools surrounding this solution to manage the environment and to secure it better. These two are areas that have caused some issues. We want to integrate it with what you call continuous integration and delivery. 

It must be scalable, cost-effective, more agile when it comes to developing and managing the environment for DevOps. All these things go together, it must be cured to allow better manageability. That is what we all are doing in most large companies.

In a future release, the solution could become more like a core engine, in which tools like OpenShift are centered. You could see how all kinds of tools could help to better improve the management, security, or scalability of the product. Additionally, we will need more than the core in our organization, there needs to be more additional management tools moving forward.

I have been using the solution for approximately one year.

When it comes to my own environment, I have had no issues with scalability but it is not easy. This is just the development environment. Regarding my company, within my department, we are running a sandbox environment just for testing and that is going well. I am not sure how things will go if you go fully into production with this solution.

We will look for additional products to deal with the difficulties with scalability. There are several vendors that offer these products. Although this solution was made for scalability, it does not come out of the box this way.

We currently have approximately 30 users using the solution in my organization.

I am not aware exactly how the on-premises installation went for the IT team at my organization. For my local environment where I am testing this solution myself, the installation has been very easy. This is mostly because it is a local environment. We also have a cloud environment, where we have a hybrid data center and this cloud environment installation was fairly easy too.

The deployment was done by an internal team in my organization. 

Maintenance is required for all software versions. We need to manage different areas of the solution such as the cloud-native landscape tooling, registry, DevOps environment, and security toolings. There are three areas that need upgrades, versioning, scalability, and the toolset surrounding the solution. You can not run it on its own, you need additional tools. All of this maintenance is taken care of by our administration IT department.

The solution is affordable.

We plan on using the solution in the future. We are a large data center and we just need to have several options available. We need to have a traditional deployment of Infrastructure as a service, with virtual machines. We need also a platform as a service for very rapid and smaller applications and container management, container as a service which is this solution for all others. We expect that the virtual machines in the next 10 years will decrease and container-based services will increase.

I recommend the solution to others. It is a very good product and the strength can be that other vendors can create their security and management toolings around it allowing it to become a type of core engine. If those other vendors were not there, I think I would be more critical. Within my department, we were a bit late adopting the solution than other parts of the organization. We are still growing and experimenting, we have some clusters already in production. A lot of the product tools are open source which in some cases means the support is also not readily available. You have to adapt to it, but also be cautious when it comes to the support and the steep learning curve issues that you can expect.

I rate Kubernetes an eight out of ten.

Kubernetes' most valuable features are scaling, deployment, and container management. Its integration with other pipeline tools is also good.

The setup process could be improved as it's quite complex, especially for newbies. In the next release, Kubernetes should include automatic deployment.

I've been working with Kubernetes for around a year and a half.

Kubernetes is a stable solution.

Kubernetes is easy to scale.

Kubernetes' technical support is good but could be a bit more responsive.

Positive

The initial setup was a bit complex.

I would rate Kubernetes as eight out of ten.