One of the main use cases for Kubernetes Everywhere is deploying applications onto Kubernetes using different multiple on-premises servers. I use Kubernetes Everywhere for deploying web applications and AI/ML models.
Hybrid deployments have unified multi-cloud apps and now demand simpler initial setup
What is our primary use case?
How has it helped my organization?
Kubernetes Everywhere has positively impacted my organization as it can be used for deploying multiple applications, multi-tenancy, and multi-cloud infrastructure. It is very simple.
What is most valuable?
The best features Kubernetes Everywhere offers is the ability to deploy once and use everywhere. Deploying is somewhat difficult, but after deploying, usage is very simple and robust.
It definitely saved a lot of time and money, and it is very effective with speed and has many features that are useful for many applications.
Kubernetes Everywhere is based on the open-source Kubernetes tool, so everything that is implemented by Kubernetes open-source should be implemented in Kubernetes Everywhere as well.
It can be seamlessly integrated with all kinds of storage, security, and other tools.
It is a very good tool with most of the features taken from Kubernetes open-source, and it works really well, is highly scalable with very low latency.
What needs improvement?
Deploying Kubernetes Everywhere infrastructure is somewhat difficult because there are many components that need to be deployed. However, once deployed, using it is very simple, taking the applications and directly deploying them using CI/CD pipelines. It works seamlessly with all kinds of CI/CD pipeline tools.
For how long have I used the solution?
I have been using Kubernetes Everywhere for the past three years.
What do I think about the stability of the solution?
Kubernetes Everywhere is very stable.
What do I think about the scalability of the solution?
Its scalability is excellent.
How are customer service and support?
The customer support is good. I would rate the customer support 10 out of 10 as they are really helpful in resolving all the issues when we are facing any problems.
How would you rate customer service and support?
Positive
What was our ROI?
It saved a lot of money and manpower.
What's my experience with pricing, setup cost, and licensing?
It is a very good tool with decent pricing, and it is not overpriced.
Which other solutions did I evaluate?
We did not choose any different solution or other tool for Kubernetes.
What other advice do I have?
I have provided all the necessary inputs. The review rating is not available.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Reliable mobile platform has delivered accurate retirement data and reduces incident rates
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Kubernetes Everywhere for a couple of years.
What do I think about the stability of the solution?
Kubernetes Everywhere is stable.
What do I think about the scalability of the solution?
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.
How are customer service and support?
The customer support for Kubernetes Everywhere is great.
I would rate the customer support on a scale of one to ten as an eight.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
I did purchase Kubernetes Everywhere through the AWS Marketplace.
What about the implementation team?
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.
What was our ROI?
I have seen a return on investment; fewer incidents are my main return on investment.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
Platform has reduced downtime and now supports flexible deployment of smaller applications
What is our primary use case?
My main use case for Kubernetes Everywhere is just enough cloud computing, which is the main intention why we are using it. Basically, when I say just enough computing, we wanted to deploy into smaller applications and reduce the T3 or kind of servers.
What is most valuable?
The best features Kubernetes Everywhere offers are its multiple ways of isolating applications and spinning them, which stand out to me the most.
I would like to add that scalability is by default one of the things in Kubernetes Everywhere, and whenever we want, we are able to increase it, which is helping.
Kubernetes Everywhere has impacted my organization positively because performance-wise, we don't have any downtimes, whereas earlier we used to have downtime. I don't have an estimate of how much our downtime has decreased since using Kubernetes Everywhere, but we tried very hard to minimize the downtime due to SLAs, and with Kubernetes Everywhere, it's effortless downtime avoidance, which is one of the beauties of Kubernetes Everywhere.
What needs improvement?
I can think of an improvement for Kubernetes Everywhere in that it should be easier to use from a developer's perspective, as it involves a lot of infrastructure numbers and DevOps. If we can make it something a developer can do, that will be great.
For how long have I used the solution?
I have been using Kubernetes Everywhere for the last three years.
What do I think about the stability of the solution?
In my experience, Kubernetes Everywhere is stable, and I haven't seen any issues.
What do I think about the scalability of the solution?
Regarding scalability, I haven't faced any scalability issues so far.
How are customer service and support?
The customer support for Kubernetes Everywhere has been very much lesser needed, and I would say support-wise, it's a 10, even though there's minimal interaction from us.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I previously used very servers before switching to Kubernetes Everywhere.
What was our ROI?
I have seen a return on investment with Kubernetes Everywhere in that we need fewer employees for sure, and we reduced the resources, which means money saved.
Which other solutions did I evaluate?
Before choosing Kubernetes Everywhere, I didn't evaluate other options much because we thought of Kubernetes, so we went ahead with that.
What other advice do I have?
My advice to others looking into using Kubernetes Everywhere is that it ensures scalability and is maintenance-free, meaning whenever we want, we should be able to update and all. I give this product a rating of 10.