kyma-project / kyma-project/runtime-watcher
Ensure consistent labeling of all resources
@lindnerby is already working on this.
Since Aug 25, 2026.
- Dominant language
- Go
- Stars
- 1
- Forks
- 18
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 10
Description
Description
Ensure consistent labeling accross all resources deployed by your module/component. According to the decision record, all resources must be labeled with kyma-project.io/module=<module-name>. The following table contains the resources deployed by your module/component without this label.
| module | namespace | kind | name | top-level-resource |
|---|---|---|---|---|
| watcher | kyma-system | NetworkPolicy | kyma-project.io--metrics-to-watcher | |
| watcher | kyma-system | NetworkPolicy | kyma-project.io--seed-to-watcher | |
| watcher | kyma-system | NetworkPolicy | kyma-project.io--watcher-to-apiserver | |
| watcher | kyma-system | NetworkPolicy | kyma-project.io--watcher-to-dns | |
| watcher | kyma-system | Deployment | skr-webhook | |
| watcher | kyma-system | Pod | skr-webhook-* | Deployment/skr-webhook |
| watcher | kyma-system | Secret | skr-webhook-tls | |
| watcher | kyma-system | Service | skr-webhook | |
| watcher | kyma-system | Service | skr-webhook-metrics | |
| watcher | kyma-system | Secret | webhook-server-cert |
It has to be ensured, the labels are added to all resources. This affects also resources created dynamically by the module/component even if they are not mentioned in the table above.
Reasons
Customers must be able to identify Kyma-related resources.
Contact
@TorstenD-SAP
ToDos [Developer]
- ...
PRs
- ...
ACs [PO]
- ...
Attachments
- ...
Follow-Up Issues
- ...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.