Bug Hunting and improvements week - what we improve on Qovery
Why did we use a full sprint for bug hunting?
While it is true that we fix bugs in every sprint (20% maximum of each sprint is dedicated to bug fixes), sometimes it is not enough to fix them all, and as you can imagine, itâs not good practice to let them live in the backlog forever. A lot of companies, such as Dashlane or MyPorsche, are working with a âZero bug policyâ, and at Qovery, we have our way to make sure that bugs are taken care of:
- In a standard sprint, we can use up to 20% of each sprint for bugs
- If our backlog is greater than 20% of bugs, we freeze the next sprint to make it a âbug only sprint.â
The reason behind that is the same as for the âZero bug policyâ if you leave bugs live in your backlog, there is a chance that they will never be fixed, and there is nothing worst for a user than seeing the same bug. Over and over!
What are the improvements?
Frontend
- (feat) filter logs by pod name
- (fix) avoid having the same colour for different pods
- (fix) refresh application metrics when switching between apps and during deployment
the next step is to add the instance type selection instead of the CPU/RAM during the cluster setup
Backend
- (fix) Special characters in database credentials can lead to unexpected behaviour (if you were using Postgres and Redis, the special characters were not well supported, and it was causing issues for the passwords that had some inside)
- (feat) [CLI] Allow using an URL to connect via the qovery shell command
- (feat) Display in logs if the Docker cache is used correctly
- (feat) Accept instance type selection in cluster setup + provide an endpoint to list available instance types
- (fix) Desired nodes should be higher or equal to min node
- (fix) Canât switch database from private to public and vice versa (container side)
- (fix) Stopping containerized databases means losing data
- (fix) âDelete organizationâ API call not working when there are no clusters
Wrapping up
While itâs true that we are putting a lot of work and effort to build our V3, we also want to make sure that we keep the V2 as stable and user friendly as possible and make changes like improving the application build-time or avoiding having the same colour for different pods may seem minor. Still, all added up; we believe that it will significantly enhance your product use.
.svg)
.svg)
.svg)
Suggested articles
At enterprise scale, managing provider-specific Kubernetes YAML across multiple clouds creates crippling configuration drift and operational toil. By adopting an agentic Kubernetes management platform, infrastructure teams abstract cloud-specific configurations (like ingress controllers and storage classes) into a single, declarative intent that automatically reconciles across 1,000+ clusters.
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.
.webp)