Skip to main content

Overview

Qovery enables centralized management of Kubernetes object annotations and labels through the console. Organizations can establish annotation/label groups in the settings, then assign them to services. Labels and Annotations Settings

Label Groups

Creating Label Groups

Access label group creation via the Add new button, then select Add label group. Required inputs include: Forbidden Label Prefixes (non-exhaustive):
  • kubernetes.io/, k8s.io/
  • qovery.com (all variants)
  • aws, eks:*
  • System identifiers: appId, envId, cluster_id, organization_id
Propagate as Tag Option: Forwards Kubernetes labels to cloud provider resources, subject to cloud-specific tag format requirements (AWS, GCP, Scaleway). Current Scope: Managed databases on AWS clusters; future releases will support environment and cluster-level tagging. Label Group Applicable to applications, cronjobs, lifecycle jobs, and databases (not Helm).

Managing Label Groups

Editing: Modify existing groups to add, remove, or update labels. Services require redeployment to reflect changes. Deletion: Remove groups; services need redeployment to remove associated labels.

Annotation Groups

Creating Annotation Groups

Select Add annotation button. Provide: Forbidden Annotation Prefixes (non-exhaustive):
  • kubernetes.io/, k8s.io/
  • meta.helm.sh/*
  • qovery.com (all variants)
  • System checksums: checksum/*, appCommitId
Scope Definition: Restricts annotations to specific Kubernetes objects (ingress, pod, deployment). Annotation Group Applicable to applications, cronjobs, lifecycle jobs, and database containers (not Helm).

Managing Annotation Groups

Editing: Update annotations or modify scope; redeployment required for active services. Deletion: Remove groups; services require redeployment to strip associated annotations.

Important Note

Helm services support direct label/annotation configuration within chart definitions; these centralized groups don’t apply.