> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/kubernetes/cd-k8s-ref/kubernetes-annotations-and-labels.md).

# Kubernetes annotations and labels

This topic describes how to use annotations and labels to select objects you defined in your manifests.

### Annotations <a href="#annotations" id="annotations"></a>

To see annotations in action, see [Deploy Manifests Separately using Apply Step](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/kubernetes/kubernetes-executions/deploy-manifests-using-apply-step.md) and [Ignore a Manifest](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/kubernetes/cd-kubernetes-category/ignore-a-manifest-file-during-deployment.md). Annotations are a way to pass additional metadata for resources to Harness. For a description of Annotations, go to [Annotations](https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/) from Kubernetes.

The following Annotations can be put on resource specifications in the Harness Service **Manifests** section.

| **Annotation**               | **Value** | **Usage** |
| ---------------------------- | --------- | --------- |
| `harness.io/skip-versioning` | "true"    | "false"   |
| `harness.io/direct-apply`    | "true"    | "false"   |
| `harness.io/primary-service` | "true"    | "false"   |
| `harness.io/stage-service`   | "true"    | "false"   |

### Labels <a href="#labels" id="labels"></a>

The following labels are applied by Harness during deployment.

| **Label**                 | **Value**            | **Usage**                                                                                                                                                                              |
| ------------------------- | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `harness.io/release-name` | `release name`       | Applied on pods. Harness uses a release name for tracking releases, rollback, etc. You can supply a release name in an Environment's Infrastructure Definition **Release Name** field. |
| `harness.io/track`        | `canary` \| `stable` | Applied on pods in a Canary deployment.                                                                                                                                                |
| `harness.io/color`        | `blue` \| `green`    | Applied on pods in a Blue/Green deployment.                                                                                                                                            |

### Next steps <a href="#next-steps" id="next-steps"></a>

* [Kubernetes Releases and Versioning](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/kubernetes/cd-k8s-ref/kubernetes-releases-and-versioning.md)