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
Static delivery pipelines are becoming a bottleneck. The best CI/CD tools for Kubernetes are those that move beyond simple code builds to provide total environment orchestration and developer self-service.
The Broadcom acquisition of VMware has sent shockwaves through the enterprise world, with many organizations facing license cost increases of 2x to 5x. If you are looking to escape rising TCO and rigid subscription bundles, these are the top vSphere alternatives for a modern hybrid cloud.
Is the "Heroku Tax" draining your budget? Compare Heroku vs. Kubernetes in 2026. Learn how to solve complex orchestration challenges, like queue-based autoscaling and microservice sprawl, without the DevOps toil.
Is the EKS operational burden outweighing its benefits? Learn how to migrate from EKS to ECS, the technical trade-offs of AWS-native orchestration, and how to get ECS-level simplicity without losing Kubernetes power.
Is the "Kubernetes Tax" killing your teamâs velocity? Compare Docker vs. Kubernetes in 2026 and discover how to get production-grade orchestration with the "Git Push" simplicity of Docker, without the operational toil.
Discover how Qovery bridges the gap between developers and infrastructure with a "security by design" approach. From federated identities and unique encryption keys to real-time audit logs and SOC2 Type 2 certification - see how we protect your data while eliminating vendor lock-in.
.webp)