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

Alessandro Carrano About 22 hours ago

Upgrade to Kubernetes 1.32

We will upgrade your managed clusters to version 1.32

Alessandro Carrano 8 days ago

Jun 30

Preview environment - customize environment name

We will let you customize the preview environment name. Today it is fixed with “[PR] - ” but we will let you compose the naming via a set of macros (example “{{PR_ID}}-preview”)

Alessandro Carrano 22 days ago

Terraform provider - Separate resource to manage cluster routing

If we had a dedicated routing table resource in the Qovery terraform provider, we could then chain 1, 2 and 3 directly: We create the cluster, and so we can get the VPC ID created by Qovery, We can then create the peering connection (using the VPC ID), that will create a connection ID, We can create the routing table using the connection ID. Today, it is in the cluster. So it requires at least two deployments: Deploy the cluster and the peering connection, Update the code to add the routing table, Re-deploy to update the cluster with the routing table.

Alessandro Carrano 29 days ago

Jun 30

Easily retrieve VPC identifiers

We will include the VPC information (ID etc..) as : environment variables: so that you can use them to deploy your resources within it via Terraform/Cloudformation etc.. in our Terraform provider: so that you can retrieve this information and deploy by yourself the required resources outside of Qovery

Alessandro Carrano About 1 month ago

Jun 30

Terraform exporter for the entire cluster

Allow to export the overall cluster and each environment within it as a terraform manifest

Alessandro Carrano About 1 month ago

Add custom nodepool for Karpenter

For Karpenter setup, we will add the possibility of creating new node pools on top of the two default ones (stable and default)

Alessandro Carrano About 1 month ago

Access environment namespace information from a service/API/Terraform provider

We will pull the information of the namespace used to deploy your environments and make it available on the UI but also on our terraform provider

Alessandro Carrano About 1 month ago

Jun 30

Access VPC information from a service/API/Terraform provider

We will pull the VPC (or similar) information from your cloud account and make them available on our control plane. These can be useful for: - deploy a terraform module that needs to know the VPC information dynamically - automate the configuration of VPC peering if you deploy your cluster via our terraform provider

Alessandro Carrano About 1 month ago

Jun 30

Provide additional Cloud provider cluster information (name, id, oidc, arn)

When qovery creates a cluster on the user cloud account, it assigns a name (usually qovery-z) and it is not visible in the UI and cannot be retrieved from the API/Terraform provider. Moreover, the cloud provider might assign its own ID and it is not retrievable through Qovery. we will provide you with those information on both the UI and the terraform provider we will also provide the oidc url and the cluster ARN

Alessandro Carrano About 2 months ago

Jun 30

Region - Support for Mexico (Central) mx-central-1

Recently the new region was launched and we would like to use that region. https://aws.amazon.com/blogs/aws/now-open-aws-mexico-central-region/

moises About 2 months ago

3

Jun 30

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 2 months ago

2

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 2 months 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 2 months 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 3 months 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 3 months 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 3 months 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 3 months 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 3 months ago

Implement DORA metrics

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

Alessandro Carrano 3 months ago