Discover 8 New Major Features on Qovery - May 2024 Edition
Watch the complete Qovery Demo Day May 2024 here.
1. Qovery on Your Local Machine
Now, you can try Qovery on your local machine with just one command: qovery demo up. The only requirements are Docker running and 2 vCPU with 4GB RAM available. This feature allows you to explore Qovery without any restrictions or time limits, completely free of charge.
Check out the announcement.
2. Bring Your Own Kubernetes with Qovery
Installing Qovery on your Kubernetes cluster is now straightforward with the command qovery cluster install. This command initiates a simple wizard that generates a Helm chart for you to review and apply. This feature is fully accessible without any restrictions or time limits, and it is free.
Check out the documentation.
3. Manage Kubernetes Annotations
Qovery now allows you to manage your Kubernetes annotations with an intuitive and powerful interface, giving you greater control over your Kubernetes deployments.
Check out the announcement.
4. Karpenter Integration
We have rolled out Karpenter, a highly cost-efficient Kubernetes node autoscaler, in public beta. Karpenter supports spot instances and GPUs, enabling significant cost savings on AWS. Learn more about Karpenter and how it can reduce your AWS costs by up to 60% here. Check out this article for deploying AI applications with GPUs on AWS EKS and Karpenter.
Click here to join the beta
5. Helm Deployment Improvement
We have simplified Helm deployments by eliminating the need to add Qovery macros into your Helm values file. Qovery now automatically injects them via a Kubernetes Admission Controller, making the deployment process smoother.
6. Qovery Cloudshell
Access your applications and databases with Qovery's remote shell access directly from your web browser. With one click, you're connected to your apps, providing a seamless remote access experience.
7. New Service List
We are continually working to simplify the deployment of any type of application within Qovery. Our new service list is designed to make this process more intuitive, ensuring quick and easy application deployment.
8. Contextual Helper
We have introduced a consistent way to offer assistance within Qovery at any point in your journey. The contextual helper provides comprehensive help from our documentation, forum, and, if needed, our support engineering team.
Bonus: Qovery Portal
Watch the end of our demo day to discover the Qovery Portal and get a sneak peek at what we are preparing for Qovery V4.
It's a wrap
Our commitment at Qovery is to make the most enjoyable Internal Developer Platform for Platform Engineers and Developers. We aim to continuously innovate and improve, ensuring that our platform remains intuitive, powerful, and developer-friendly. Stay tuned for more exciting updates and features as we strive to enhance your development experience.
.svg)
.svg)
.svg)
Suggested articles
Kubernetes is a distributed orchestration engine that automates container deployment and scaling. At an enterprise level, its core mechanisms—control planes, schedulers, and worker nodes—provide foundational infrastructure resiliency. However, operating these components natively across thousands of clusters creates massive configuration drift, requiring intent-based control planes to manage Day-2 FinOps, RBAC, and multi-cloud abstraction globally.
Kubernetes autoscaling relies on three dimensions: horizontal (pod count), vertical (resource size), and cluster (node count). While CPU-based scaling is standard, enterprise fleets require advanced Day-2 strategies (such as custom Prometheus metrics and priority-class overprovisioning) to prevent node boot delays and memory bottlenecks during severe traffic spikes.
Agentic Kubernetes resource reclamation is the practice of using an autonomous control plane to continuously identify, suspend, and delete idle infrastructure across a multi-cloud Kubernetes fleet. It replaces manual cleanup and reactive autoscaling with intent-based policies that act on business state, eliminating the configuration drift and cloud waste typical of unmanaged fleets.
Kubernetes is an open-source container orchestration engine. At enterprise scale, it abstracts infrastructure to automate deployment, scaling, and networking. However, managing hundreds of clusters introduces severe Day-2 operational toil, requiring agentic control planes to enforce global governance, security policies, and cost optimizations across multi-cloud fleets.
The shift from AI copilots to autonomous agents is redefining infrastructure requirements. Discover how to build secure, stateful, and compliant Agentic AI systems using Kubernetes, sandboxing, and observability while meeting EU AI Act standards
Effective Kubernetes management in 2026 demands a shift from manual cluster building to intent-based fleet orchestration. By implementing agentic automation on standard EKS, GKE, or AKS clusters, enterprises eliminate operational weight, prevent configuration drift, and proactively control cloud spend without vendor lock-in, enabling effective scaling across massive fleets.
A Kubernetes single pane of glass is a centralized management layer that unifies visibility, access control, cost allocation, and policy enforcement across § cluster in an enterprise fleet for all cloud providers. It replaces the fragmented practice of switching between AWS, GCP, and Azure consoles to govern infrastructure, giving platform teams a single source of truth for multi-cloud Kubernetes operations.
Deploying a Docker container on Kubernetes requires building an image, authenticating with a registry, writing YAML deployment manifests, configuring services, and executing kubectl commands. While necessary to understand, executing this manual workflow across thousands of clusters causes severe configuration drift. Enterprise platform teams use agentic platforms to automate the entire deployment lifecycle.
.webp)