Kubernetes Annotations and Labels
Harness applies labels during Kubernetes deployment that you can use to select objects you defined in your Harness Service Manifests section.
Annotations are a way to pass additional metadata for resources to Harness. For a description of Annotations, see Annotations from Kubernetes.
The following Annotations can be put on resource specifications in the Harness Service Manifests section.
By default, all the ConfigMap and Secrets resources are versioned by Harness. Corresponding references in PodSpec are also updated with versions.
A managed workload in Harness is a workload taken to steady state and verified at steady state. If it fails to reach steady state, rollback occurs.
An unmanaged workload is simply run without checking for steady state.
For example, a Canary Deployment requires a minimum of 1 Deployment or StatefulSet as a managed workload. You can deploy additional workloads in the deployment by using the
Identifies the primary Kubernetes service in a Blue/Green deployment.
Identifies the Kubernetes stage service in a Blue/Green deployment.
The following labels are applied by Harness during deployment.
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.
Applied on pods in a Canary deployment.
Applied on pods in a Blue/Green deployment.