As shared in our product roadmap, we have been working on improving the naming of the resources deployed on your Kubernetes cluster, adding the environment and service name in the naming convention instead of just our own internal ids.
As an example, the namespace name will change from:
env-z<qovery_environment_id>-<sanitizied_env_name>Where <sanitizied_env_name> is a cleaned version of the environment name that you chose on the Qovery platform (Example: env-z2843c942-front-end)
A similar naming convention is adopted for the other resources deployed on the cluster like Deployments, StatefulSets, Jobs, Cronjobs etc…
This feature has been released today and applies only to any new environment or service created on your Qovery organization.
The new naming convention applies only to any new environment or service created on your Qovery organization.
We couldn’t roll out this change massively since changing names for Kubernetes resources is disruptive and would cause service downtime. Especially for namespaces, there’s no way to automatically rename them.
Once a service/environment is created, we automatically assign it a “kubernetes name”. This Kubernetes name is the one used to create the resources on your cluster and cannot be changed afterwards.
For the same reason as above, we will not let you update this name. We might open the possibility to edit the name for services but it will be at your own risk of causing a downtime on your applicaiton.