Later

Reviewing

Roadmap

See and create backups for your databases

👀 Reviewing

Manage database Backups

albane tonnellier

Support Hetzner (Cloud Provider)

Utkarsh Kanwat

Extend Qovery with Sentry, e.g. for release tracking

Add ons - Sentry integration

Guillaume Gelin

Make Qovery supporting managed RabbitMQ. As a user I don't want to think about restarts, health checks, or ensuring the service is running. I don't want to mess with the config to make it fast.

Managed RabbitMQ

Make Qovery supporting managed Kafka. As a user I don't want to think about restarts, health checks, or ensuring the service is running. I don't want to mess with the config to make it fast.

Managed Kafka

In heroku it's very easy to capture a database backup and download it. It would be helpful to be able to do something similar here straight from the qovery shell.

Add ability to dump database from Qovery Shell

Kevin

Support OVHcloud

Catdrout

I have an environment that has Start &amp; Stop enabled, and a cron job build failed, but the whole environment deployment was cancelled. A cron job build error should not cancel the whole environment.<img src="https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/1713336664867..png">

Cron Job build error should not cancel environment deployment

Moises Alejandro

Amazon has also been making Aurora a first class citizen within AWS for a while now especially with Amazon Aurora 2 coming out soon. I'd expect AWS will continue to push people to use Aurora over normal RDS PostgreSQL/MySQL DBs.So it would be amazing if Qovery could suppot Amazon Aurora. This "serverless" DB would greatly decrease costs for some users if they don't have constant load and be great for users with spikey and unexpected loads.

Support for Amazon Aurora

Aaron Hammer

Allow to disable pulling files that are included in git lfs.Sometimes we have many files in lfs, but don't need them during build, and our build times are currently slowing down

Allow to disable git LFS

Tim S.

Sometimes I may need to store files on S3. Eg: I have a service that received images from users, I need to save the images and expose them publicly.

🔙 In Product Backlog

S3 storage

Support Docker Compose file to configure a Qovery environment and deploy complete apps.

Support Docker Compose file

We should review the name and provide the important info somewhere else. Important info list:PR titlePR numberCreation timestampBranch name

Improve the information available on preview environment (title, branch, pr etc..)

We will deliver a new cluster view allowing you to better understand the current cluster consumption and what is consuming the most

Cluster usage view

Alessandro Carrano

We will let you define a TTL for your environment after which the environment will be automatically stopped and deleted. It will make sure that your environments won't run for nothing and you keep control on your cloud cost

Add environment TTL

The feature to deploy Managed Database via Qovery is really really useful and nice.However it is not possible:<ul><li>to select the instance type. For the moment it is limited to "t3" kind.</li><li>to configure multi-az</li><li>to configure encryption at REST for data storage.</li><li>(in container mode) to change the number of replica (only 1 possible)</li></ul>This is not possible event for "Production" (Qovery tag) environment. Usually, a Production requires to be deployed in multi-AZ, using instances with CPU available all the time (not t3 like) and with encryption for data.Doing such configuration for managed DB (and maybe other managed services) would be really appreciated.

Enhance Managed Database configuration options

Jean-Philippe Fourès (IG1)

today you can already change the icon of your service by selecting one among a pre-selected set. we will give you the possibility to upload your own custom icon

Add your own custom icon for services

Allow to deploy in a blue/green way, moving the traffic from the blue to the green environment on demandIt will help to easily validate that all works on a new version by creating a copy of our production env.

Blue/Green deployment

We will improve the way you can access the application logs. While you will still be able to query the logs via the Qovery console, we will simplify the access to the Loki instance and make it scale based on the query load. You will be able to deploy your own Grafana and query the logs as you wish.

Improve log stack to secure access via other tools (like grafana)

We have already delivered the feature to customize the tag for the managed databases deployed with Qovery (see <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://roadmap.qovery.com/p/customize-labelstags-on-resources-4">https://roadmap.qovery.com/p/customize-labelstags-on-resources-4</a>). With this feature, we want to let you customize also the tag of the infrastructure resources deployed with a Qovery cluster like the one attached to the EKS cluster, EC2 nodes etc..

Customize tag for Qovery clusters

We will improve the current deployment log view, integrating our AI Copilot to find the root cause and provide you with a solution

✏️ In Development

Improve deployment error troubleshoot via AI Copilot

We will integrate ArgoCD into our product, allowing you to deploy argocd applications or migrate them to the Qovery stack

ArgoCD Integration

We will work on integrating the most commonly used secrets manager directly into the product, without having to manage this directly in your application

Secrets manager integration

We will replace the NGINX ingress controller since it will be decommissioned by the end of Q1. The plan is to replace it with Envoy Gateway

NGIX Ingress controller deprecation

we will review the product navigation to ensure the different product features are well visible in the product: <ul><li>manage your production</li><li>ephemeral environments</li><li>etc..</li></ul>

New product navigation

⏭️ Next

Dark mode

We will provide more information on the deployment of your applications by providing you with the time that was necessary to: - Pull the source code - Build the app - Deploy the app The information will be available on both the deployment tab and the deployment log screens

Provide stats on deployment times

We will support MySQL 8.4 for both container and managed database (only AWS RDS)

Support MySQL 8.4

We will provide a simplified way to use service accounts on your application with Qovery deployment. today the users have to follow this guide which has a lot of steps and it's error prone https://hub.qovery.com/guides/tutorial/use-aws-iam-roles-with-qovery/

Simplify configuration of Service account for applications

We will allow you to restrict intra-cluster communication by letting you configure network policies

Restrict intra-cluster communication

We will upgrade your managed cluster to version 1.35

Upgrade to Kubernetes 1.35

We will upgrade your managed cluster to version 1.34

Upgrade to Kubernetes 1.34

we will improve the existing service list by providing a set of templates to deploy the most common cloud resources

Qovery Service Catalog

We will improve the structure of the deployment logs to better distinguish the steps of the deployment and give you an idea of the time it took for each step

Improve deployment logs readiness

SPA usually store assets on a cdn or S3 bucket. today we let this deploy via a contenerized application but instead we should support the deployment of front-end apps directly on a S3 or CDN