logging-operator
logging-operator copied to clipboard
kube-logging
Orphan ClusterFlow and ClusterOutput resources are not reflected in their status
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.
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] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
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!
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!
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.