Tell Qovery how they could make the product more useful to you.
Have something to say?
⏭️ Next
Notification center
we will build a single notification page where important information will be pushed to all the members of your organization.
✅ Done
Copilot read-write mode
we will unlock the write mode, with an approval step to ensure that write operations are explicitely accepted by the end user
⏭️ Next
Split build and deployment process
We will separate the build process from the deployment one, allowing you to trigger the build of the app at any time without having to deploy it.
⏭️ Next
Promotion flows
we will introduce a built-in promotion system allowing you to move an application version across different environments up to the productiokn one
⏭️ Next
Customize Kubernetes add-ons - introduce cluster layers
we will introduce more flexibility in your cluster configuration by introducing cluster layers. each layer corresponds to a specific application stack deployed on the cluster (for example observability etc..) some layers will be available by default and manged by qovery. You’ll be able to customize those layers or add new one
✅ Done
Improve deployment error troubleshoot via AI Copilot
We will improve the current deployment log view, integrating our AI Copilot to find the root cause and provide you with a solution
✅ Done
ArgoCD Integration
We will integrate ArgoCD into our product, allowing you to deploy argocd applications or migrate them to the Qovery stack
⏭️ Next
Restrict intra-cluster communication
We will allow you to restrict intra-cluster communication by letting you configure network policies
✏️ In Development
Qovery Blueprints
we will improve the existing service list by providing a set of blueprints to deploy the most common cloud resources
✅ Done
Secrets manager 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
✏️ In Development
NGIX Ingress controller deprecation
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
✅ Done
Audit logs - provide diff
We will add the “diff” information in the audit logs, making it more powerful and allowing you to quickly identify what has changed at a certain point
✅ Done
Scaleway - support static IP
We will allow you to define a static IP for your cluster on all your egress traffic
✅ Done
Qovery Observability - RDS Monitoring
We will provide a way for you to monitor the RDS instances deployed with Qovery (CPU, disk etc..).
✅ Done
Copying postgresql access uri should contain 'postgresql://'
When accessing our postgresql through public credentials, the “copy to clipboard” function is really helpful. However, when I paste that into the terminal for psql -d or a sql tool, I always need to add the protocol prefix to the string manually. If possible, it would simplify the workflow to have it included in the clipboard contents.
Make service description visible on service listing
I’m documenting our use of Qovery for our team. I’ve filled out the “description (optional)” boxes in the settings for each service, but that information doesn’t seem to go anywhere. When an engineer opens an Environment, they’re greeted with a list of services. The name is somewhat helpful, but in order to get any further explanation they need to navigate into the service settings. With the goal of providing living documentation, it would be helpful to surface the description in the Services page so that it can be used to direct our staff without needing to consult out of band documentation.
✅ Done
Qovery Observability - Alerting system
we will build an alerting system for our Qovery observability product!
✅ Done
GPU provisioning native support
We will natively integrate in Qovery the provisioning of GPU instances. You will be able to define the type of machine and as well the number of GPUs that your application needs to run