Files
awx-operator/docs/user-guide/advanced-configuration/labeling-operator-managed-objects.md
kurokobo 2b0221bbc6 docs: overall minor renovations (#1874)
* docs: simplify README.md and make index.md to refer to it
* docs: change order for pages in navigation and add missing pages
* docs: fix headings to improve navigation, transform notes to admonition, fix indentation, linting issues and minor issues
* docs: merge docs for using images from private registries
* docs: add example to integrate LDAP configuration via extra_settings_files
* Apply suggestions from code review
docs: apply suggested changes

Co-authored-by: Don Naro <dnaro@redhat.com>

* docs: update the doc site url as same as the url in https://www.ansible.com/ecosystem/
* docs: minor fixes for hpa page
* docs: expand note block
* docs: apply #1904 to README.md

---------

Co-authored-by: Don Naro <dnaro@redhat.com>
2024-07-20 18:34:21 -04:00

1009 B

Labeling operator managed objects

In certain situations labeling of Kubernetes objects managed by the operator might be desired (e.g. for owner identification purposes). For that additional_labels parameter could be used:

Name Description Default
additional_labels Additional labels defined on the resource, which should be propagated to child resources []

Example configuration where only my/team and my/service labels will be propagated to child objects (Deployment, Secrets, ServiceAccount, etc):

apiVersion: awx.ansible.com/v1beta1
kind: AWX
metadata:
  name: awx-demo
  labels:
    my/team: "foo"
    my/service: "bar"
    my/do-not-inherit: "yes"
spec:
  additional_labels:
    - my/team
    - my/service
...