My main use case for Kubernetes Everywhere is to have a centralized infrastructure where I can manage and orchestrate all the containers in one place.

The main thing that makes the container orchestration of Kubernetes Everywhere stand out for me is the scalability and the ability to have it controlled. We can set the number of nodes we want to auto-scale up to, and we can also have dedicated memory and CPU usage for each of our applications, so that we ensure we are not overloading any nodes.

The main impact of Kubernetes Everywhere on my organization was cost because we were using different cloud platforms and different services. Since we started using Kubernetes Everywhere, we brought all the applications in one place. This impacted the speed, security, and cost, and mainly the data, so the data stays in one place.

There was an improvement in the deployment pipeline because of the Helm charts that we use with Kubernetes Everywhere. In terms of speed, speed was 50% faster than what it was before. In terms of cost, we were able to save up to 40% of the DevOps cost.

The best features that Kubernetes Everywhere offers is the container orchestration.

The best way to improve Kubernetes Everywhere is to implement AI agents which can dive deeper and it will be easy for the tech enthusiast or tech expert to just chat with that agent, so that we don't have to spend hours in debugging and finding the root causes of server downtime.

I have been using Kubernetes Everywhere since the last two years.

Kubernetes Everywhere is stable.

Kubernetes Everywhere's scalability is definitely great.

Customer support for Kubernetes Everywhere could be better.

Previously I used Google's App Engine and I had to switch to Kubernetes Everywhere because as I mentioned previously, we wanted to bring everything to one cloud platform.

I would rate the customer support of Kubernetes Everywhere at eight on a scale of one to ten. I think they should thoroughly check the documentation for Kubernetes Everywhere because that is where 90% of the information is. I would give this product an overall rating of nine.

My main use case for Kubernetes Everywhere is managing production and development clusters for updating and maintaining clusters, nodes, and upgrading the node Kubernetes version as required. I sometimes have to create new clusters for short-term use cases.

The best features Kubernetes Everywhere offers me in my work are scalability and zero downtime deployment. We can upgrade application versions with zero downtime.

Kubernetes Everywhere has positively impacted my organization by providing lower costs, flexibility, and scalability. We can spin up a new application in a few seconds or minutes, and we can secure applications using ingress.

I think Kubernetes Everywhere could be better for me. Two years ago, I faced ingress-related issues where our application exposes multiple ports and we bind different DNS with different ingress configurations. When we combined multiple ingress configurations into a single one, it created issues that took approximately three to four months to resolve. Any better way to handle ingress would be helpful.

The ingress issue is the main concern for me because I continue to face ingress-related issues most of the time. However, all other aspects work well if you follow the documentation.

I have been familiar with Kubernetes Everywhere for around five or more years.

I can quantify the impact on deployment time. Deploying an application at the instance level takes approximately one week. Deploying the same application on Kubernetes Everywhere takes one week for the first deployment, but subsequent deployments require only one day.

I suggest that someone considering using Kubernetes Everywhere for the first time should follow the documentation carefully. If you follow the steps methodically, you can easily deploy anything. However, if you search randomly online and run commands without understanding them while trying to launch a cluster and deploy a live application, you may encounter difficulties. I would rate this product an eight out of ten.

My main use case for Kubernetes Everywhere is that we are using Google Cloud in our organization, and security is based on Kubernetes on GCP.

A quick, specific example of how I use Kubernetes Everywhere with GCP is that we have our own AI tool which is deployed via Terraform to GCP, and we use GCP in day-to-day life.

Additionally, I want to add that we have our portal, portal login, API security, and all the services are deployed entirely on GCP.

The best features Kubernetes Everywhere offers for my team or organization are that it has both a UI interface as well as the command interface for day-to-day activities.

The UI and command interface help me in my daily activities because we have our own software which is deployed on the portal, and our portals are deployed in Kubernetes clusters. Whenever the pods are failing, we get errors such as memory out of unit in Java JVM, allowing us to reboot the pods and have them come up. We can do this via UI as well as with GCP commands, and on the Kubernetes side, we can connect to any cluster which has issues and resolve the problems.

Kubernetes Everywhere has positively impacted my organization with cost savings, where we have a good amount of savings around sixty thousand to seventy thousand USD per year. It is pretty efficient, fast, and it has reduced our downtime as well.

Kubernetes Everywhere can be improved if it had more convenient commands, which would make it easier for me to remember all the commands in GCP for Kubernetes.

I have been using Kubernetes Everywhere for three to four years.

Kubernetes Everywhere is stable in my experience.

Kubernetes Everywhere has good scalability features, and I have seen it scale pods up to three hundred, making it pretty scalable and fast.

I have reached out to the Google Cloud team for customer support, but it is not as good compared to the AWS support team.

I have not previously used a different solution before Kubernetes Everywhere.

Regarding my experience with pricing, setup cost, and licensing for Kubernetes Everywhere, I have not deployed it from scratch, so I am not aware of the pricing and the setup cost. However, I know that we have the licensing for the next three years.

Before choosing Kubernetes Everywhere, I have not evaluated other options personally, but my organization would have done that.

I rate Kubernetes Everywhere a nine out of ten.

I choose nine out of ten because the commands are a little bit tricky to remember, causing me to reduce one point.

My advice to others looking into using Kubernetes Everywhere is to go with it; it is very good and reliable in the market.

I have no additional thoughts about Kubernetes Everywhere before we wrap up; I am all good. My overall review rating for Kubernetes Everywhere is nine.

I cannot definitively say what the main use cases for Kubernetes Everywhere are since it can be utilized with multiple different projects. It can be used effectively for CI/CD integration with no complexity and is easy to use, providing many benefits.

Kubernetes Everywhere is most beneficial when you have machine learning workloads or AI workloads, as it is particularly useful for those scenarios.

I have very limited use cases with Kubernetes Everywhere and do not have a full scale deployment.

Kubernetes has its own fault tolerance and can automatically bring up a pod whenever there are any interruptions. Kubernetes default functions such as DaemonSets and other features services provide a rich fault tolerance.

We use Ingress in Kubernetes Everywhere to load balance multiple workloads.

The initial setup of Kubernetes Everywhere is good, and the documentation provides clear instructions.

Kubernetes Everywhere is easy to operate when you have a settled environment and easy to manage. It offers high availability and fault tolerance with all high availability features, a rich support of latest technologies, vulnerability management, and easy management.

I have not been using Kubernetes Everywhere for a long time, but I recently came across it. I have good hands-on experience with Kubernetes from the past three to four years, but with Kubernetes Everywhere for only the past six months.

Due to poor planning of the application developers and resource management, I have seen crashes, downtimes, and performance issues. Different scenarios have occurred where applications went offline, some applications ran into performance-related issues, and some had connectivity issues. I have to go through these situations and identify the specific case in each instance.

I have tried to scale it up and scale it out for Kubernetes Everywhere. Unfortunately, Kubernetes Everywhere does not have an automatic scale-up tool, but I have done scaling and scaling down manually.

It would be a great feature if Kubernetes Everywhere could provide default monitoring and alerting instead of depending on Prometheus and Grafana.

Past one year.

Due to poor planning of the application developers and resource management, I have seen crashes, downtimes, and performance issues. Different scenarios have occurred where applications went offline, some applications ran into performance-related issues, and some had connectivity issues. I have had to identify and fix these issues in specific cases.

I had issues with our private cloud, and we have a private cloud vendor, which is Mirantis Kubernetes. Multiple cases were raised with them, and unfortunately, they did not have any fixes initially. They eventually came to us with some fixes to address the issues that we encountered.

For tech support with Kubernetes Everywhere, I would rate it between eight to nine out of ten.

The initial setup of Kubernetes Everywhere is good, and the documentation provides clear instructions.

I do not have hands-on experience with hybrid cloud for Kubernetes Everywhere. I have done some work on-premise, but I am moving toward a hybrid model that is currently in the test phase. As of now, I could not describe any benefits regarding hybrid cloud.

Managed file transfer and Kubernetes Everywhere are two different use cases, and I do not see major differences between them. I cannot compare both products.

My overall review rating for Kubernetes Everywhere is eight out of ten.

My main use case for Kubernetes Everywhere is for mobile integrations.

I do not use Kubernetes Everywhere for patients; this is for mobile channel integrations where we serve our participants financial information about their retirement.

Kubernetes Everywhere helps with these integrations primarily regarding reliability.

What makes Kubernetes Everywhere reliable for my team is that, since I mentioned, it's financial information, we have to provide accurate information to our participants, and it's specifically retirement; we do not want to give incorrect data. So, we rely on Kubernetes Everywhere to provide that information accurately so that our participants are not given incorrect information, and it also saves our brand reliability with our participants.

The best feature Kubernetes Everywhere offers is the reliability feature, which mostly impresses me.

What makes the reliability stand out for me is uptime and error handling; also, as I mentioned previously, it's providing reliable data, which is very important for us in TIAA because it is the retirement data that we serve, and we do not want to provide anything incorrect to our participants. As this is a 100-year-old company, we want to make sure our participants are given the accurate information, reliable information that they deserve.

Kubernetes Everywhere has impacted my organization positively by being reliable as well as providing accurate data, maintaining the uptime, which is very important, and making sure we deliver the accurate data that is required by our participants.

I have seen specific outcomes, with incidents having definitely reduced drastically from what it was a few years back; so certainly, I can see there is more than 25 to 50% reduction in the incidents since adopting Kubernetes Everywhere.

At this time, I may not have any improvement suggestions; I want to explore more, so the features currently provided satisfy me, but if there is anything Kubernetes Everywhere can share with modernization, that would be great.

Keeping up with new technologies was exactly on my mind; if we can be provided information about those new technologies that can modernize would be helpful.

I have been using Kubernetes Everywhere for a couple of years.

Kubernetes Everywhere is stable.

I may not have much more insight into its scalability at this time because, as I have been mentioning in the previous inputs, I'm focused on reliability; hence, at this time, I may have to dig deeper into the scalability aspect of it.

The customer support for Kubernetes Everywhere is great.

I would rate the customer support on a scale of one to ten as an eight.

I may have to check on what solution we previously used before Kubernetes Everywhere, but from the time we switched to Kubernetes Everywhere, it has been reliable and helped with incident reductions.

I did purchase Kubernetes Everywhere through the AWS Marketplace.

The experience with pricing, setup cost, and licensing is handled by our enterprise pricing team, but what I feel is for the reliability that it provides; I'm sure the pricing would have been according to discussions with the enterprise team.

I have seen a return on investment; fewer incidents are my main return on investment.

Before choosing Kubernetes Everywhere, I think we were pretty much interested in it; we went with that option, and in our organization, it's done at the enterprise level, so we were provided Kubernetes Everywhere, which was really great for us to use.

My advice for others looking into using Kubernetes Everywhere is to look at its reliability options and how it can help reduce incidents and keep the environment stable. I would rate this review an eight out of ten.