> ## Documentation Index
> Fetch the complete documentation index at: https://www.qovery.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Labels & Annotations

> Manage Kubernetes labels and annotations for your organization

## 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.

<img src="https://mintcdn.com/qovery/ziWdn5St6rf4bcBc/images/configuration/organization/annotations_labels_settings.png?fit=max&auto=format&n=ziWdn5St6rf4bcBc&q=85&s=64f7a7d2238e29f53975ec0615ef242c" alt="Labels and Annotations Settings" width="3164" height="2070" data-path="images/configuration/organization/annotations_labels_settings.png" />

## Label Groups

### Creating Label Groups

Access label group creation via the `Add new` button, then select `Add label group`. Required inputs include:

* Group name identifier
* Key/value pairs following [Kubernetes label syntax](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set)

**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 and AWS clusters; future releases will support environment-level tagging.

<img src="https://mintcdn.com/qovery/ziWdn5St6rf4bcBc/images/configuration/organization/label_group.png?fit=max&auto=format&n=ziWdn5St6rf4bcBc&q=85&s=5b8e66d9bf943ea92bba43a95488ad92" alt="Label Group" width="3164" height="2070" data-path="images/configuration/organization/label_group.png" />

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:

* Group name
* Annotation key/value pairs per [Kubernetes annotation syntax](https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/#syntax-and-character-set)
* Kubernetes scope (e.g., `ingress`, `pod`, `deployment`)

**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).

<img src="https://mintcdn.com/qovery/ziWdn5St6rf4bcBc/images/configuration/organization/annotation_group.png?fit=max&auto=format&n=ziWdn5St6rf4bcBc&q=85&s=11954ea50ab9a180387e62ec128e8899" alt="Annotation Group" width="3164" height="2070" data-path="images/configuration/organization/annotation_group.png" />

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.