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
Scaling your deployments to zero is only half the battle. If your cluster autoscaler does not aggressively bin-pack and terminate the underlying worker nodes, you are still paying for idle metal. True environment sleeping requires tight integration between your ingress layer and your node provisioner to actually realize FinOps savings.
The biggest mistake enterprises make when evaluating Kubernetes management platforms is confusing infrastructure provisioning with Day-2 operations. Tools like Terraform or kOps are excellent for spinning up the underlying EC2 instances and networking, but they do absolutely nothing to prevent configuration drift, automate certificate rotation, or right-size your idle workloads once the cluster is actually running.
For years, Red Hat OpenShift has been the safe choice for heavily regulated, on-premise environments. It operates as a secure fortress. But in the public cloud, that fortress acts as an expensive prison. Paying proprietary per-core licensing fees on top of your standard AWS or GCP compute bill is a redundant "middleware tax." Escaping OpenShift requires decoupling your infrastructure from your developer experience by running standard, vanilla Kubernetes paired with an agentic control plane.
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 focuses on container orchestration, but the reality on the ground is far less forgiving. Provisioning a single cluster is a trivial Day-1 exercise. The true operational nightmare begins on Day 2. Teams that treat multi-cloud fleets like isolated pets inevitably face crushing YAML configuration drift, runaway AWS bills, and severe scaling bottlenecks.
Rancher solved the Day-1 problem of launching clusters across disparate bare-metal environments. But in 2026, launching clusters is no longer the bottleneck. The real failure point is Day-2: managing the operational chaos, security patching, and configuration drift on top of them. Rancher is a heavy, ops-focused fleet manager that completely ignores the application developer. If your goal is developer velocity and automated FinOps, you must graduate from basic fleet management to an intent-based Kubernetes Management Platform like Qovery.
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
.webp)