Determine system namespaces by label

kyma-project / telemetry-manager

Manager for the Kyma telemetry module

https://kyma-project.io/#/telemetry-manager/user/README

Apache License 2.0

5 stars 24 forks source link

Determine system namespaces by label #380

Open a-thaler opened 11 months ago

a-thaler commented 11 months ago

Description The namespace filters of the telemetry pipelines are providing a convenient way to exclude system namesapces. That set of namespaces is hardcoded currently which does not fit with the concept of modularization as modules might run in other namespaces. Instead the set of namespaces should get collected dynamically based on labels. Will require that all modules are following https://github.com/kyma-project/community/issues/864

Criterias:

When running in a managed cluster, the system namespaces should be determined fully if one of this labels are present
- reconciler.kyma-project.io/managed-by: reconciler
- operator.kyma-project.io/managed-by: lifecycle-manager
When running local or in a test setup, the managers namespace should get selected only
There is no hardcoded list of namespaces in the source code

Reasons

Attachments

kyma-bot commented 7 months ago

This issue or PR has been automatically marked as stale due to the lack of recent activity. Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

After 60d of inactivity, lifecycle/stale is applied
After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle stale
Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

github-actions[bot] commented 5 months ago

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 3 months ago

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 1 month ago

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.