Allow export of all users with Qovery access

We perform quarterly access reviews of our service. The users have to be manually extracted from the “Members” page today. It would be helpful to be able to export our users, their role, and their last login as a CSV.

Kyle Flavin About 24 hours ago

Access to repositories via a GitHub application

We will revamp the existing Qovery GitHub application that has been decommissioned a few months ago.

Alessandro Carrano 12 days ago

Helm diff command

we will create a new action helm diff capable to run a helm diff on the helm charts you deploy with Qovery. This will allows you to verify what will happen on a configuration change (values file modified for example) before deploying the chart

Alessandro Carrano 15 days ago

disable modifications when resources are managed via TF provider

allow to disable modifications via the UI/CLI on any resource that it is managed via the Qovery TF provider. a safety mechanism has to be planned to ensure that editing is still allowed in case of issues

Alessandro Carrano 29 days ago

More fine-grained permission management

we would like to have a more fine-grained permission management so that we could create roles with a fully customized composition of roles.

Alessandro Carrano 29 days ago

Deploy a temporary debug pod

sometimes you need to connect via shell to your application to run specific commands. To avoid impacting your production application and maybe set custom resources, we will allow you to deploy a temporary debug pod as a copy of one of the running application.

Alessandro Carrano 29 days ago

Use service a dependency system instead of deployment stages

We will move out from the stages system and instead use a dependency system to define the deployment pipeline. For example: you will be able to define that : a service A depends on the service B a service C depends on nothing a service D depends on B and C Qovery will automatically execute the deployments based on these dependency and you won’t have to define stages anymore.

Alessandro Carrano 29 days ago

Blue/Green deployment

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

Alessandro Carrano 29 days ago

Implement DORA metrics

We will provide you with some of the DORA metrics based on the data available in Qovery

Alessandro Carrano 29 days ago

Simplify export of deployment logs to Datadog

Simplify the export operation of the deployment logs to Datadog

Alessandro Carrano 29 days ago

Autoscaling based on custom event/metrics

We would like to configure the application autoscaling based on custom event/metrics instead of the standard CPU/Memory consumption (Ex: queue delay etc..)

Alessandro Carrano 29 days ago

Support MySQL 9.1

we will add the support of MySQL 9.1 for both container and managed databases (only AWS RDS)

Alessandro Carrano About 2 months ago

Allow to manage roles via TF provider

We will allow you to manage the roles of your organization via our terraform provider

Alessandro Carrano About 2 months ago

Advanced application log access

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.

Alessandro Carrano 2 months ago

Mar 31

Qovery webhook compatible with Discord

Unfortunately, webhook compatibility only works with the Slack platform. It would be a great help if this tool was compatible with Discord.

Pedro Comenda 3 months ago

Support PostgreSQL 17

we will support the version 17 of postgresql for both container and managed db (only AWS RDS)

Alessandro Carrano 3 months ago

1

Dec 31

Support MySQL 8.4

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

Alessandro Carrano 3 months ago

1

Mar 31

[AWS] Use assume role authentication (STS) instead of access_keys

on AWS: Instead of relying on an access key based authentication, we should use a role based authentication via the STS system

Alessandro Carrano 3 months ago

Mar 31

Autoscaling parameters

Hello, we find the Qovery autoscaling very limited. It only allows to change the CPU or memory (hpa.cpu.average_utilization_percent or hpa.memory.average_utilization_percent) to start scaling the instances/pods. Qovery checks those parameters every 5 minutes. We find it not enough. With just adding a couple more of parameters it would be competent autoscaler. How difficult would be allowing to define the poll period and the number of instances we want to scale each time? Thank you.

Juan José Cermeño Portet 3 months ago

4

Configure rate limit for nginx ingress

We will allow you to configure the nginx rate limit parameters so that you can better protect your exposed services here you can find the official nginx parameters that you will be able to configure https://docs.nginx.com/nginx-ingress-controller/configuration/ingress-resources/advanced-configuration-with-annotations/#rate-limiting

Nanou 4 months ago

1

Mar 31