Replies: 1 comment
-
|
Yes, having a patches:
- target:
kind: Deployment
name: source-controller
patch: |
- op: add
path: /spec/template/metadata/labels/app.kubernetes.io~1name
value: source-controller
- target:
kind: Deployment
name: kustomize-controller
patch: |
- op: add
path: /spec/template/metadata/labels/app.kubernetes.io~1name
value: kustomize-controller
- target:
kind: Deployment
name: helm-controller
patch: |
- op: add
path: /spec/template/metadata/labels/app.kubernetes.io~1name
value: helm-controller
- target:
kind: Deployment
name: notification-controller
patch: |
- op: add
path: /spec/template/metadata/labels/app.kubernetes.io~1name
value: notification-controller
- target:
kind: Deployment
name: image-reflector-controller
patch: |
- op: add
path: /spec/template/metadata/labels/app.kubernetes.io~1name
value: image-reflector-controller
- target:
kind: Deployment
name: image-automation-controller
patch: |
- op: add
path: /spec/template/metadata/labels/app.kubernetes.io~1name
value: image-automation-controller
I do not see how adding a label to manifests will be an issue. Maybe even migrating from generic Is it worth bumping to an issue? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
There is a number of recommended labels for Kubernetes and it seems Flux manifests comes with most. However
app.kubernetes.io/nameis not part of the default labels. I was wondering if there is any reason for this label not being there?Beta Was this translation helpful? Give feedback.
All reactions