AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Kubernetes annotations example9/9/2023 Using release- as a prefix will prevent any issues. Kubernetes service and pod names follow DNS-1035 and must consist of lowercase alphanumeric characters or '-', start with an alphabetic character, and end with an alphanumeric character. For example: Figure 9: A YAML file with a ytt. By default, the value Harness uses is release-$. A ytt annotation is a YAML comment of a specific format it attaches behavior to a node. ![]() You can supply a release name in an Environment's Infrastructure Definition Release Name field. examples/k8s/traefik-rbac.yaml kubectl apply -f For namespaced restrictions, one RoleBinding is required per watched namespace along with a corresponding configuration of Traefiks kubernetes.namespaces parameter. Harness also uses a release name for tracking releases. you might want to skip versioning is for an ImagePullSecret because it never changes, or for TLS certs if they are referred to in Kubernetes container command args. You do not need to reference versions when using Secrets.įor cases where versioning is not required, the manifest entered in the Harness Service Manifests section should be annotated with harness.io/skip-versioning: "true".įor example. ![]() Versioning does not change how you use Secrets.
0 Comments
Read More
Leave a Reply. |