search

kube-logging / logging-operator

Logging operator for Kubernetes
https://kube-logging.dev
Apache License 2.0
1.53k stars 326 forks source link

Orphan ClusterFlow and ClusterOutput resources are not reflected in their status #700

Open pepov opened 3 years ago

pepov commented 3 years ago

The status of the ClusterFlow and ClusterOutput resources should highlight when they are not in the configured controlNamespace.

Solution idea: collect all the ClusterFlows and ClusterOutputs with other logging resources that are not matching with the control namespace as well and then go through them in the validationreconiler to update their status.

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!

pepov commented 11 months ago

All flow and output resources should have their managing logging resource's name in their status, so that we can easily identify those resources that are orphan.