Q & A - What annotations can be applied in Harness?

harness.io/skip-versioning: "true" → For cases where versioning is not required (which Harness stores in a ConfigMap in your Cluster) → Kubernetes Versioning and Annotations | Harness Developer Hub

harness.io/direct-apply: "true"|"false" → Set to true to make a manifest an unmanaged workload. For example, Harness Canary and Blue Green steps support a single Deployment or StatefulSet workload as a managed entity, but you can deploy additional workloads as unmanaged using the harness.io/direct-apply annotation. → What can I deploy in Kubernetes? | Harness Developer Hub

annotations: harness.io/primary-service: "true" && annotations: harness.io/stage-service: "true" → If you have more than one service, Harness does not automatically know which is the primary service unless you add the annotations like this (Blue/Green Deployments) → Create a Kubernetes Blue Green deployment | Harness Developer Hub

harness.io/skipPruning: "true" → To ensure that a resource is not pruned (the resource must have been deployed by harness) → Prune Kubernetes resources | Harness Developer Hub

The following labels are applied by Harness during deployment. → Kubernetes annotations and labels | Harness Developer Hub

Run Step Setting for Unit Testing. → Run Tests step settings | Harness Developer Hub

KOTS ingress controller annotations (deprecated) → Add ingress controller annotations | Harness Developer Hub

Chaos Engineering IAM role and policy for service account → IAM Integration for AWS Authentication | Harness Developer Hub