Kubernetes Everywhere Reviews

My main use case for Kubernetes Everywhere involves different clusters, and currently, I'm working on product features that provide backup and restore for Kubernetes, so I have worked from deploying Kubernetes to writing operators as well.

A specific example of how I use Kubernetes Everywhere for backup and restore in my daily work includes the new product we are creating, which is a backup and restore solution for Kubernetes, and I'm developing new features every day, with a Vcluster setup where we create different Kubernetes clusters, and I also work on a GKE cluster and OCP.

As a product, we are using Kubernetes Everywhere, but in my free time, I just use it for deploying my different resources or personal projects that I deploy on Kubernetes and run on the server.

The best features Kubernetes Everywhere offers include its scalability; if you have a small system to deploy on Kubernetes, you can just keep a single pod running, and as traffic increases, you can use a scale command to scale your system easily, which is quite helpful.

The scalability feature impacts my day-to-day work because we haven't seen much scale ourselves, but our customers using our product really find it helpful to scale their Kubernetes cluster during traffic spikes, as our product provides easy backup and restore, which simplifies disaster recovery.

Kubernetes Everywhere positively impacts our organization by making it quite easy to deploy different microservices for different languages; we simply build the Docker container and pass it to the YAML, and if anything breaks, debugging is straightforward because we know exactly where the issue is coming from.

This ease of deployment and debugging has affected my team's productivity positively, as we observe that with the ease of microservices, we can catch bugs quickly, unlike earlier when we had a monolithic system running on a single binary, making it difficult to find root causes; now, with components deployed as different microservices running in separate pods, debugging is much easier.

I think all the features that Kubernetes provides have been very helpful, but to improve Kubernetes Everywhere, increasing the speed of releases and prioritizing certain features based on community votes might make it easier.

I find the documentation quite good; Kubernetes has verbose and friendly documentation, and the community is supportive; joining Slack or other online platforms makes it easy to resolve issues, but there is always room for improvement.

I have been using Kubernetes Everywhere for four years now.

Kubernetes Everywhere is stable in my experience, and I can confirm it is reliable.

The scalability of Kubernetes Everywhere is quite straightforward, with a horizontal pod autoscaler CR allowing us to specify metrics for pod scaling, and we can also run the kubectl scale command for manual scaling.

Customer support for Kubernetes Everywhere is very good; since we use Google Cloud, whenever we face issues, they respond quickly and efficiently.

Previously, we were using Docker, which served us well until we discovered Kubernetes; the ease of deployment and ability to manage customer spikes made switching to Kubernetes a clear choice.

We have seen a return on investment primarily in terms of time savings, as using Kubernetes allows us to scale and work on the product more efficiently, spending less time on deployments and focusing more on customer demands.

Regarding pricing, setup cost, and licensing, running a Kubernetes cluster can be costly depending on the use case; however, running on GCP GKE is cheaper compared to AWS, making it relatively economical in our case.

Before choosing Kubernetes Everywhere, we evaluated Docker Swarm, which is somewhat similar, but we found Kubernetes to be more useful due to its vibrant community and heavy industry adoption.

For others looking into using Kubernetes Everywhere, I advise that if you have a large enough product that is tedious to deploy or manage, switching to Kubernetes is beneficial; however, for smaller teams with fewer customers, sticking with monolithic systems or Docker might suffice. I rate this product a ten out of ten.