Now
2Actively being built
Qovery Blueprints
we will improve the existing service list by providing a set of blueprints to deploy the most common cloud resources
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
Next
13Committed and queued
Provide stats on deployment times
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
Support MySQL 8.4
We will support MySQL 8.4 for both container and managed database (only AWS RDS)
Simplify configuration of Service account for applications
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/
Notification center
we will build a single notification page where important information will be pushed to all the members of your organization.
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.
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
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
Restrict intra-cluster communication
We will allow you to restrict intra-cluster communication by letting you configure network policies
Improve deployment logs readiness
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
Better support front-end application deployment
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
Later
61Committed and queued
S3 storage
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
Support Docker Compose file to configure a Qovery environment and deploy complete apps.
Improve the information available on preview environment (title, branch, pr etc..)
We should review the name and provide the important info somewhere else. Important info list: PR title PR number Creation timestamp Branch name
Cluster usage view
We will deliver a new cluster view allowing you to better understand the current cluster consumption and what is consuming the most
Add environment TTL
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
Enhance Managed Database configuration options
The feature to deploy Managed Database via Qovery is really really useful and nice. However it is not possible: to select the instance type. For the moment it is limited to "t3" kind. to configure multi-az to configure encryption at REST for data storage. (in container mode) to change the number of replica (only 1 possible) 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.
Add your own custom icon for services
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
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.
Improve log stack to secure access via other tools (like grafana)
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.
Reuse container images across environments by default
When deploying an application from a container image, we have a mirroring process copying the image on the image registry attached to the cluster (more information here) we will improve this part and ensure we mirror only once the same image name / tag across all the environments, speeding up the deployment time
Reviewing
46Under consideration
Manage database Backups
See and create backups for your databases
Support Hetzner (Cloud Provider)
Support Hetzner to deploy applications.
Add ons - Sentry integration
Extend Qovery with Sentry, e.g. for release tracking
Managed RabbitMQ
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 Kafka
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.
Add ability to dump database from Qovery Shell
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.
Support OVHcloud
OVH support
Cron Job build error should not cancel environment deployment
I have an environment that has Start & 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.
Support for Amazon Aurora
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.
Allow to disable git LFS
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