Kubernetes Reviews

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. 

I am currently learning the system, connecting the containers, and assessing the power of it.

The most valuable feature is the support for Docker containers.

The management needs to be improved.

I have been working with Kubernetes for approximately five months.

To this point, we have not needed to contact technical support.

The initial setup is a little bit complex for non-technical people in the business domain. It takes about a month to deploy.

Our in-house team is responsible for deployment and maintenance.

This is a good product and I can recommend it. That said, it will be better in the future.

I would rate this solution an eight out of ten.

It is a very good solution for deploying microservices in an application. It has a lot of freedom in it, which makes it very interesting. 

It is also web-enabled. You can run services in other virtual applications and virtual machines. 

It would be useful to have a basic and stable interface for monitoring and quick deployment purposes, especially when the deployments are big like a proof of concept or proof of technology. Currently, you need to use the Kubernetes console for all functionalities. 

It is not a quick-to-learn product if you are not from a Linux background. You need to be very skilled at Linux to learn it quickly. It took me two to three months because I mostly work with Microsoft products. For people who are not from a Linux background, the learning curve is a little bit longer.

It is very scalable, and it expands very well. Scalability is a very useful and important feature, especially when you work in a cloud environment.

It is scalable for an enterprise. You can scale up or scale down depending upon the environment or deployment. You can scale vertically with the size of the nodes. You can also scale the number of nodes. 

If you are using a service, you don't really need any initial setup. You just deploy it in a physical or virtual environment. 

Its deployment and configuration are very easy for open systems. I have experience in working only with Red Hat, and the deployment is very automatic. 

I would recommend this product. It is very close to being a 100% agnostic solution. It is just a step away from becoming a server-less solution like Fusion, which, although, is designed for running for a short time.

I use Kubernetes on the platform layer to deepen a platform. In some cases, when the same solution was developed without Kubernetes, some customers had issues on platforms like AWS, Azure, and Google.

I would rate Kubernetes an eight out of ten.

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.

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.

I primarily use Kubernetes to manage containers.

Kubernetes' most valuable features include scalability and deployment.

Kubernetes' VM functionality and security could be improved. 

I've been using Kubernetes for six months.

I would rate Kubernetes' stability eight out of ten.

I would rate Kubernetes' scalability ten out of ten.

The initial setup is straightforward so long as you have an understanding of the product. Deployment takes around forty-five minutes to an hour.

We implemented using an in-house team.

I would recommend Kubernetes to other users and rate it ten out of ten.