Improvement: Environment Variables and Secrets Management
Project and Environment Env Var Views
Previously, configuring environment variables required delving into each service individually. Now, you can set these variables directly from the project and environment views. This new feature eliminates unnecessary steps, allowing you to manage your environment variables conveniently and efficiently.
Bulk Actions for Environment Variables
We understand that handling multiple environment variables can be time-consuming. To address this, we've introduced bulk actions. You can now select multiple environment variables and perform bulk deletions in one go. This capability significantly reduces the time and effort needed to manage large sets of variables.
Simplified Scope Selection
We have improved the scope selection for environment variables to prevent errors and streamline the process. Now, only the relevant scope options are displayed when setting a variable. This change eliminates confusion and ensures you can only select available scopes.
Wrapping up
These updates are designed to simplify the management of environment variables, saving time and reducing potential errors. We believe these enhancements will make your experience with Qovery even better.
We will incorporate more improvements in future releases, so stay tuned for updates, and as always, happy coding!
.svg)
.svg)
.svg)
Suggested articles
To stop GPU costs from destroying SaaS margins, teams must transition from static to consumption-based infrastructure by utilizing Karpenter for dynamic provisioning, maximizing hardware density with NVIDIA MIG, and leveraging Qovery to tie scaling directly to business metrics.
AI is helping developers write more code, faster than ever. But writing code is only half the story. What happens after? Building, deploying, debugging, scaling. That's where teams still lose hours.We're building Qovery for this era. Not just to deploy your code, but to make everything that comes after writing it just as fast.
By adopting GitOps and utilizing management platforms like Qovery, fintech teams can automatically generate DORA-compliant audit trails, transforming regulatory compliance from a manual, time-consuming chore into an automated, native byproduct of their infrastructure.
Kubernetes success is determined by Day 2 execution, not Day 1 deployment. While migration is a bounded project, maintenance is an infinite loop that often consumes 40% of senior engineering capacity. To protect margins and velocity, enterprises must transition from manual toil to agentic automation that handles scaling, security, and cost.
Day-0 is planning, Day-1 is deployment, and Day-2 is the infinite lifecycle of maintenance. While Day-0/1 are foundational, Day-2 is where enterprise operational debt accumulates. At fleet scale (1,000+ clusters), managing these differences manually is impossible, requiring agentic automation to maintain stability and eliminate toil.
A multi-cluster Kubernetes architecture distributes application workloads across geographically separated clusters rather than a single environment. This strategy strictly isolates failure domains, ensures regional data compliance, and guarantees global high availability, but demands centralized Day-2 control to prevent exponential cloud costs and operational sprawl.
.webp)