-
Notifications
You must be signed in to change notification settings - Fork 15
[RFE] Update labelling flow #11
Copy link
Copy link
Open
Description
The labelling approach with Kustomize assumes the resource definition is part of the bases or manifests and for that reason does not work well for existing elements like nodes, Pods or deployments.
The labelling flow should account for:
- Follow GitOps principles and have a continuous remediation cycle
- Work for labeling any objects that already exists on a cluster (e.g. nodes, secrets, pods, etc)
- Should work when the consumed by GitOps controllers
Example of options to investigate:
- The use of Kustomize Transformers
- Using OPA Gatekeeper (https://github.com/open-policy-agent/gatekeeper)
- Using resource-locker-operator (https://github.com/redhat-cop/resource-locker-operator)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels