Feature Ideas

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.

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

Grafana, Prometheus, and Loki are already installed on the cluster for internal Qovery use. I would like to be able to set up Prometheus to fetch metrics from our applications and use Grafana to analyze them. Also it would be nice to have access to Grafana for more powerful log querying from Loki.

Sometimes the operation to delete a cluster is stuck because Qovery can't access the cluster or your cloud account anymore (Different reasons: credentials not valid anymore, cluster deleted on the cloud account etc..) or simply you want to delete everything without having to manually delete each environment. We will add a few options on the cluster delete action allowing you to: delete the environments and cluster only on Qovery side (mostly when the credentials are not valid anymore and you have already deleted everything on your cloud account) delete the environments on Qovery side AND delete the cluster on the cloud provider (mostly when you don't want to manually delete each environment linked to this cluster but you still want a proper clean of the resources created by Qovery on your cloud account)

Today, we provide some information on how the product works within the product itself but not all of it can fit in our screens. A lot of information is available in our public documentation or our public forum but you have to look for it, making you ask for help if you can find the right information. We will improve the support flow to ensure you access the right information at the right time.

We will upgrade all managed clusters to the kubernetes version 1.28 (at least AWS)

By default our API Tokens have the same permissions as the admin of the organization. We will allow you to manage the permissions by assigning a role to your API token (similar to what you can do with the organization members via the RBAC)

Support GCP to deploy applications

Support Azure to deploy applications

Native support of Datadog as a monitoring platform in Qovery. Important Note: Datadog is already supported in Qovery but we want to provide better integration. Contact us or put a comment if you have any questions.

See and create backups for your databases

Vote fore all views in dark

Allows team members to login from a Google account. Today we can only login via GitHub, and most developers have their personal email there. Allowing to connect via Google would let us connect via our work email address.

Add the possibility to add custom tags / labels on the resource managed by Qovery that should be replicated on the cloud provider entities (clusters, pods, managed databases etc..). This will make it more simple to monitor those resources via the standard monitoring tools (datadog etc..)

It seems like any time an environment variable is updated, a re-deploy with full image re-build is required. This takes a long time. Re-deploys should be optimized as much as possible in case of urgent updates. The rebuild is probably required in case the new variables are needed during image building, but in most cases that is probably not needed. Suggest a way to identify variables that when changed, a new image build is required, vs variables that when changed, simply need the container's environment updated. Or, maybe this can be controlled via docker file layers by the customer, in which case this feature idea is unnecessary. But the goal would be to be able to update a "runtime" variable and redeploy quickly.