Kubernetes Reviews

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.

Kubernetes is a container management platform. 

I use it to be able to sell it to my customers. I am evaluating it and its general features.

I would like to have more knowledge and a good understanding of Kubernetes, what it can do, and what the use cases are to meet the customer's requirements or environment. 

By using it, I can properly advise the clients of what Kubernetes can, and can't do.

Scalability is the most valuable feature.

With Kubernetes, you also get High Availability.

Kubernetes can be used for most companies, but for some companies that may be too small, it may not be worth the investment, as it is expensive.

I have been working with Kubernetes for two years.

We are using the latest version.

Kubernetes is a stable product.

Kubernetes is a scalable product.

We have multiple sales teams, some are responsible for large enterprises businesses, some for medium-sized companies.

The documentation they have available is good.

I have not contacted technical support. 

Much like other products such as Red Hat, for example, have their own support.

I work with any product that is related to Kubernetes.

The initial setup was straightforward. 

It's simple, and it is easy to deploy.

We provide implementation services for our clients as well as maintenance.

In addition to Kubernetes, you have to pay for support.

The price could be cheaper.

They offer many different licensing models. There are many options to choose from.

I would recommend this solution to others. 

It is my job to do this and I feel that it is the future of every company.

We are integrators, and we are working on becoming partners, to obtain the certificate.

I would rate Kubernetes a nine out of ten.

Our primary use case of this solution is to maintain the container orchestration. Our platform is mostly containerized and our solution needs Kubernetes because it was developed in a containerized environment. We are end-users. 

The Kubernetes cluster is easy to maintain on the container orchestration. It's very stable with outward scalability and good performance which is very important for our platform. Kubernetes is a good choice to maintain the containerized application and solution. 

Scalability is good but I'd like to see it improved with more user-friendly operability. 

I've been using this solution for about 18 months. 

The solution is stable. 

The solution is scalable.

Installation of the Kubernetes manifest file is quite straightforward. We have close to 800 users. My team has two engineers who deal with any issues. 

I highly recommend this solution and rate it 10 out of 10. 

The use case in this organization is basically to containerize the applications. It covers both the operational and technology side. I work in the train industry here and that is a medium-sized enterprise. I'm a cloud architect and we are customers of Kubernetes. 

A valuable feature is the management of containers and not having to worry about the high availability or scalability, especially when launching it in the cloud. I like that they provide a managed platform as a service, and you don't really have to worry too much about the master nodes that control the workloads. You tell them what you want: This is a minimum number of container instance, or a maximum number of container instance in this tier. It automatically gets taken care of. What I like about Kubernetes is that it actually manages the containers for you so there are no concerns  regarding availability. If something fails, it launches another one and it scales out which is good. 

That's a good question. I'm not that experienced but there are definitely challenges in Kubernetes, if you are managing the cluster yourself. So doing all the admin work, managing the masters, there are some learning curves involved. If some of those things could be simplified, that would be awesome.

I've been dealing with this solution for around four years. 

Kubernetes is quite stable and has pretty wide community support. Even the enterprises are using it so if you're talking about a stable release and the nightly build and those sorts of things, definitely the enterprise use the latest stable build. And then, when they come across any issues they probably look for the next release or maybe batches and whatnot. But I guess it's fairly stable and it's just like any other open source solution. And the fact is that it's backed by so many large companies, especially Google, so there's no stability problem at all.

The scalability of this solution is fine. 

Deployment is pretty quick. I haven't done much of a bigger scale deployment as such, generally small to medium scale deployment and I've made use of the cloud-based approach. I don't have any issues there. 

I like the solution but it depends on the size of your workload. For example, Docker is good for a very small workload or maybe if you are just deploying using Docker, building and deploying your CICD-based tasks. But if you require a more complex solution, using containers or maybe when you have a high traffic workload, even with simple architecture, you might be looking at Kubernetes to optimize the workload.

There are other solutions on the market like Serverless, I would use that in preference to Kubernetes which can sometimes be difficult to manage. You can always make use of Serverless. For that reason, I would rate Kubernetes a seven out of 10. 

We are platinum partners with Oracle and we are preferred partners with Microsoft. I work for an organization which is on both sides of the coin. We are a service integrator organization. We don't have a specific loyalty, we blend in and provide the services. I'm a solutions architect.

I like the interface of this solution. When you're using it in real time, it seems to be a little easier to use versus the other options. 

If you're using the solution on the desktop, you eventually have to download the Azure package and install it before you can actually use the Azure commands in Kubernetes. There are more community packages that have been released, rather than releases by Kubernetes. I understand that it's an open server and people can contribute to it, that's how it works. However, sometimes people get misguided and that's where we need some support. It would make a difference. 

I've been using this solution for almost three months. 

It's a pretty stable solution. We have about 40 plus people who use it.

I would turn to community support as a first step. The blogs, which cover it, have given me a little bit more insight in terms of how and what and all of that. But when it comes to community, I've not asked much, but I've learned from it. I've watched some videos and see there is some online free training. I haven't been in a situation where I needed external support from Kubernetes.

We used to use Dockers. We explored Kubernetes because we want to do market platform, which is basically a show or an article together and we wanted to use a single platform for both Oracle and Azure. Not that Dockers didn't do it, but we did kind of wonder what would be the better option. 

The initial setup was relatively easy. I mean I've obviously used some of the apps before, but this seemed to be a little easier for me. I think when I used it in the Azure implementation earlier this year, it didn't give me too much heartburn although it takes a little bit more than you expect. I can just start the QP CDL and push out the command and start it. If I'm using it with Dynatrace, it's the same thing, but when it came to deploying the package into the local machine and then running it, and then trying to get the right connection within Azure it was more difficult. 

I would recommend going through the training to see what the limitations are within Kubernetes. There's not a lot of training, but what training is available should be used so people can understand the difference between Docker and Kubernetes. If somebody has used Docker previously, they can see the difference even though the methods are the same. It's the same madness, but it will help you to better position things like command line interfaces.

We had a bit of a struggle when I was trying to implement it in Azure. But if you look at the Oracle implementation, it worked really well so I would rate this solution a seven out of 10. 

Kubernetes is for orchestration. We use it for various large microservice-based architectures and web services. That's the ideal use case, but it's suitable for any kind of service that can be decomposed and needs to be scaled. Of course, it's much easier to deploy services that are stateless. It requires more skills to deploy anything stateful or data-based.

Kubernetes is a bit complex, and there's a steep learning curve. At the same time, I cannot imagine how it could be easier.  You need many add-ons to it, and the commercial releases of Kubernetes should address that. 

For example, Red Hat OpenShift comes with all the add-ons included, but Kubernetes itself is free software so, of course, you need some skills to use it.

I've been using Kubernetes for four years.

Kubernetes is highly stable, but it's a complicated system with complex dynamics, so it needs to be monitored constantly.

Kubernetes' scalability is good. We have participated in operating clusters with hundreds of nodes.

Kubernetes is an open-source solution, so there is no tech support. You have to look up solutions online. You can purchase tech support, but we haven't used that service so far.

We used Marathon Mesos in the past, but it's obsolete these days.

Installing Kubernetes is complex. You need extensive skills and knowledge to do it from scratch.I didn't do install the solution by myself. A colleague is an expert in this, so he handled it. 

You can probably deploy the bare-bones cluster within days, but it requires some study, which can take much longer. And if you want extra features, it will take more time. Kubernetes has a lot of features, so it could take three days or three weeks to deploy if you keep adding to it.

We are focusing on open-source Kubernetes that doesn't require a license, but we use OpenShift for customers. It's a licensed, supported solution by Red Hat.

I rate Kubernetes nine out of 10. I recommend Kubernetes, but it's not for the faint of heart. Deploying Kubernetes from scratch is a real technical challenge because you need to understand lots of technology. 

It's much easier to start with Kubernetes from some cloud provider or use a commercial solution like OpenShift. Doing the pure vanilla open-source Kubernetes is possible but requires expertise, which is hard to come by.

We have many use cases for Kubernetes. We manage internal microservices, running MinIO from it which is a distributed storage solution. We have GitLab and many other internal tools that we've converted and set up to Kubernetes and microservices. Our users are mainly software developers who currently number around 60, but we're planning to increase to 100 users in the coming year. We are customers of Kubernetes.

A valuable feature of Kubernetes is its high availability. It's really scalable and more efficient for resource management on the bare metal server on which it runs as opposed to vSphere or pretty much anything else that we've tried before. 

The solution is still complex to manage. It requires specialists to the extent that I wouldn't be able to ask a junior employee to manage the software.

I've been using this solution for six months. 

The solution is stable. 

The solution is scalable, you can't get more scalable than Kubernetes.

Kubernetes is community-based so we don't pay for support. 

The initial setup is quite complex. 

The solution is free. 

This is a good product but because of the management complexity I rate it eight out of 10.

We use Kubernetes to provide distribution systems for storage and for the control plane manager.

Kubernetes offers a lot of great features such as scalability and great portability of applications.

I think that the GUI dashboard in Kubernetes is very simple and that there are no great options. Also, it is a very simple HTML GUI. So the Kubernetes community should provide a central and better GUI for managing pods and containers.

I've been working with Kubernetes for around two years.

Kubernetes is very stable.

It is very scalable. If you become a master in Kubernetes, you can provide great configurations to be scalable.

I have to install Kubernetes clusters based on the machines. I spent around one hour to install a Kubernetes cluster with three servers for the master node and around 50 servers for worker nodes.

I implemented it myself.

I would recommend Kubernetes, especially, to development teams and DevOps engineers. 

On a scale from one to ten, I would rate it at ten.