Follow-up of #188
When stackablectl (and in the future our Cockpit) deploys resources into a Kubernetes cluster, we and the user are currently unable to properly identify them afterwards. Adding a common set of labels to the resources we deploy will solve this issue.
Operators should not be labeld with any Stack or Demo, they are not part of a Stack, rather a Stack depends on operators to be present.
Relevant ticket to consider: stackabletech/stackablectl#187
### Tasks
- [ ] Improve existing ADR (https://docs.stackable.tech/home/nightly/contributor/adr/adr031-resource-labels). Also decide on how the user configures custom labels in our operators.
- [ ] Enable operators to label the resources that they deploy with completely custom labels (to be refined)
- [ ] Enable operators to label the resources that are part of a demo/stack to add the demo/stack label (requires the previous task)
Follow-up of #188
When
stackablectl(and in the future our Cockpit) deploys resources into a Kubernetes cluster, we and the user are currently unable to properly identify them afterwards. Adding a common set of labels to the resources we deploy will solve this issue.Operators should not be labeld with any Stack or Demo, they are not part of a Stack, rather a Stack depends on operators to be present.
Relevant ticket to consider: stackabletech/stackablectl#187