Kubernetes Everywhere can be improved by providing an easier way for users to handle commands and developing a UI-based approach to make it easier for developers and semi-technical users, as well as focusing on improving containerization.
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.
Even though Kubernetes Everywhere is a great product, there is still room for improvement. I would say the improvements in the security part. It completely matches our rigid regulatory compliance framework. Also, the features built-in auditing for CIS benchmarks. It automatically blocks risky runtime behavior such as unauthorized root cause or unsafe credential export.The step-by-step documentation explicitly defines how to connect external hardware platforms using standard Helm charts or lightweight agent connectors.
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.
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.
Consultant at a tech vendor with 10,001+ employees
Real User
Top 20
Feb 2, 2026
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.
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.
Director, Mobile & Online Channel at a financial services firm with 10,001+ employees
Real User
Top 20
Dec 3, 2025
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.
Manager, Information Technology at a financial services firm with 10,001+ employees
Real User
Top 20
Dec 3, 2025
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.
There are many areas where Kubernetes Everywhere can be improved, such as the defining of resource limits and requests. Accurately setting CPU and memory requests and limits for pods prevents resource starvation and ensures efficient scheduling. Improvements can be made in terms of performance and availability by implementing monitoring and logging. The usage of multiple master nodes can be enabled, along with security enhancements such as prioritizing VPC design and regular updating and patching. Streamlining of CI/CD pipeline could be enhanced. Integration of Kubernetes Everywhere into CI/CD pipelines for automated deployments and updates can be improved. The optimization of container images and the choice of appropriate node types can also be enhanced.
Kubernetes Everywhere simplifies the deployment and management of applications across multicloud environments, offering a unified approach to container orchestration. It facilitates efficient integration and adaptability, enhancing operational continuity for enterprises.
Kubernetes Everywhere provides a comprehensive platform that supports application scaling, load balancing, and automated updates, ensuring seamless operations across cloud ecosystems. Designed for modern cloud infrastructure,...
Kubernetes Everywhere can be improved by providing an easier way for users to handle commands and developing a UI-based approach to make it easier for developers and semi-technical users, as well as focusing on improving containerization.
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.
Even though Kubernetes Everywhere is a great product, there is still room for improvement. I would say the improvements in the security part. It completely matches our rigid regulatory compliance framework. Also, the features built-in auditing for CIS benchmarks. It automatically blocks risky runtime behavior such as unauthorized root cause or unsafe credential export.The step-by-step documentation explicitly defines how to connect external hardware platforms using standard Helm charts or lightweight agent connectors.
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.
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 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.
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.
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 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.
There are many areas where Kubernetes Everywhere can be improved, such as the defining of resource limits and requests. Accurately setting CPU and memory requests and limits for pods prevents resource starvation and ensures efficient scheduling. Improvements can be made in terms of performance and availability by implementing monitoring and logging. The usage of multiple master nodes can be enabled, along with security enhancements such as prioritizing VPC design and regular updating and patching. Streamlining of CI/CD pipeline could be enhanced. Integration of Kubernetes Everywhere into CI/CD pipelines for automated deployments and updates can be improved. The optimization of container images and the choice of appropriate node types can also be enhanced.