Kubernetes Everywhere Reviews

My main use case for Kubernetes Everywhere is to implement a highly cost-optimized and highly available infrastructure for our applications that are used by clients and our vendors.

A specific example of how I use Kubernetes Everywhere in my environment is through our web-based application, where we have deployed code written in Node.js and React, containerized everything, pushed it to our Git registry, and run a CI/CD pipeline to deploy everything across all environments and all platforms.

In my day-to-day life, I maintain everything to ensure it is highly available, implementing cluster auto scaling and using horizontal pod auto scaler and monitoring tools, all aimed at providing a highly available and cost-optimized solution for our application.

We deploy Kubernetes Everywhere in a hybrid model, utilizing both public and private cloud infrastructures.

Our cloud providers are Hetzner and AWS.

We handle monitoring and logging with Kubernetes Everywhere using tools like Grafana, Prometheus, and Loki, enabling us to monitor our application's uptime effectively.

To ensure compliance and meet regulatory requirements when using Kubernetes Everywhere, we employ third-party tools like Wazuh and Zabbix to monitor and secure our servers against threats.

For disaster recovery, we take daily backups of our cluster to ensure recovery in case of issues.

The impact of Kubernetes Everywhere on my workflow and the team's productivity is significant because it resolves earlier issues of bugs taking a lot of time to fix, as everything is contained within pods, allowing developers and testers to directly address any application bugs efficiently.

Kubernetes Everywhere has positively impacted our organization by enabling us to focus on cost optimization and making our applications highly available and cost effective, such as using features for automated staging environments that are only active during business days.

The specific outcomes I have observed since using Kubernetes Everywhere include noticeable savings on our cloud provider invoices, which have encouraged further use of Kubernetes Everywhere, alongside improved efficiency in application monitoring and productivity.

One of the best features Kubernetes Everywhere offers is support on all platforms, such as Debian, Ubuntu, and Windows, allowing us to write the same code everywhere and simply deploy it once the image is created.

There are many good features in Kubernetes Everywhere, and it has evolved from its initial brittleness that caused frequent 503 or 504 errors to a much more stable system, which has seamlessly increased our team's productivity and improved our workflow.

I believe Kubernetes Everywhere can be improved by integrating AI to enhance its functionality, being cautious about security when managing cloud secrets, and making Kubernetes Everywhere more useful for everyone.

Security is a crucial feature for improvement, and having tools or dashboards for managing cluster costs and suggesting optimizations, like appropriate CPU allocation, could enhance the user experience when integrated with AI.

Kubernetes Everywhere's governance and security are primarily the responsibility of our company, while Kubernetes Everywhere provides features like keeping secrets secure within pods, so we must enhance the security aspect if AI is integrated.

I have been using Kubernetes Everywhere for seven to eight years.

Kubernetes Everywhere is stable.

Scaling workloads with Kubernetes Everywhere is automated.

Scalability is managed effectively by the features of Kubernetes Everywhere itself.

I have not needed to contact customer support, as we have been utilizing the documentation provided.

We transitioned from our on-premises solution that used plain Kubernetes, which prompted our switch to Kubernetes Everywhere.

The main challenge during the initial deployment of Kubernetes Everywhere was implementing security policies to ensure a secure setup, which was a significant phase for us.

Initially, my team found it somewhat challenging to learn and adopt Kubernetes Everywhere, but after about a month, we became accustomed to it and now use it frequently.

Although we have not seen a clear return on investment in terms of reduced personnel, we are already operating with a lean structure that aligns with our cost optimization goals, independent of Kubernetes Everywhere.

My experience with pricing, setup cost, and licensing with Kubernetes Everywhere is based on at least five years of focus on cost optimization.

We chose Kubernetes Everywhere over other solutions because it excelled in comparisons with our research on alternatives.

Our evaluations primarily focused on open-source solutions, steering us away from paid options, which influenced our decision to choose Kubernetes Everywhere.

I would recommend Kubernetes Everywhere to anyone looking for a simple hybrid multi-cloud Kubernetes management tool on PeerSpot.

I rate Kubernetes Everywhere an eight out of ten because I consider the aspects of security and AI integration that need attention, but overall, it is good to have.

The accuracy and reliability of Kubernetes Everywhere's AI capabilities depend on how well the prompts are structured, as a well-defined prompt leads to better outcomes, highlighting the importance of prompt engineering in achieving accuracy.

Upgrades and maintenance with Kubernetes Everywhere are very easy, and we seamlessly upgrade our nodes and Kubernetes versions without significant challenges, aside from custom VPN setups for client database connections.

My main use case for Kubernetes Everywhere is as an orchestrated agent to make my Docker containers communicate among themselves and host a web app.

I use Kubernetes Everywhere as an orchestrated agent in my day-to-day work to handle data which has around 10 million-plus rows. When I tried to deploy my app using a single Docker file, it took more time to deploy and my web app was slow. I decided to create a Kubernetes file where I created an orchestrated agent in which multiple Docker containers communicate among themselves and all my rows are segregated among themselves and posted separately. Using this approach, I can make my web app work faster and more efficiently so that my client can use it seamlessly.

Kubernetes Everywhere offers the best feature in that I can write a Docker file in a very human-readable format, allowing any person without any coding knowledge to code it in Kubernetes Everywhere.

The human-readable format of Kubernetes Everywhere has helped my team because we are working in a field where we do not require any tech knowledge, but only for web app-related things do we need tech to be incorporated. As a non-tech person who needs to create a web app, Kubernetes Everywhere is very helpful so that, with the help of AI and other Google forums, we can create a web app seamlessly, making it very useful.

Kubernetes Everywhere has positively impacted my organization because we do not require any tech background to make our web app work. It is very helpful and is impacting our organization in a very good manner.

I can share that there has been a reduction in required technical staff because for hosting a web app, we previously needed to hire a new technical person. However, because of using Kubernetes Everywhere, we have saved costs by not needing to hire an employee, allowing one person in our team to manage these changes.

Kubernetes Everywhere is pretty good, but it can be improved in terms of reliability and speed because currently, it takes around two to three minutes to deploy my entire app, possibly due to the weight of the codes I have or some outages from the platform side. It would be helpful if they increase the deployment speed of Kubernetes Everywhere.

I have been using Kubernetes Everywhere for the past one and a half years.

Kubernetes Everywhere is pretty stable already.

The scalability of Kubernetes Everywhere is good because it works for multiple operating systems, including Linux and Windows, and it can be scalable among multiple regions, making it pretty much helpful.

The customer support for Kubernetes Everywhere is good as well; they have a very good community forum, so whenever we have some doubts, we can refer to their community websites and forums, which is pretty good.

We did not previously use any solution at all, so we went with Kubernetes Everywhere from scratch only.

We did not evaluate any other options before choosing Kubernetes Everywhere.

I definitely advise others looking into using Kubernetes Everywhere to consider it because it does not require any tech knowledge. Anyone can create Kubernetes Everywhere files, and if they have minimal tech knowledge, they can be able to create it and do their work. Therefore, I suggest them to go with Kubernetes Everywhere before considering any other choices. I gave this product a rating of ten out of ten.

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.