Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
pepov opened this issue Mar 9, 2021 · 1 comment
Labels
bug Something isn't working go Pull requests that update Go code good first issue Good for newcomers pinned
Milestone

Comments

@pepov
Copy link
Member

pepov commented Mar 9, 2021

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.

@pepov pepov added the bug Something isn't working label Mar 9, 2021
@stale stale bot added the wontfix This will not be worked on label Apr 12, 2023
@pepov pepov removed the wontfix This will not be worked on label Apr 16, 2023
@pepov pepov added this to the 4.2 milestone Apr 17, 2023
@stale stale bot added the wontfix This will not be worked on label Jun 16, 2023
@aslafy-z aslafy-z removed the wontfix This will not be worked on label Jun 16, 2023
@pepov pepov modified the milestones: 4.3, 4.x Jun 27, 2023
@stale stale bot added the wontfix This will not be worked on label Aug 26, 2023
@aslafy-z aslafy-z removed the wontfix This will not be worked on label Aug 26, 2023
@pepov
Copy link
Member Author

pepov commented Oct 9, 2023

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.

@pepov pepov added the pinned label Oct 9, 2023
@pepov pepov modified the milestones: 4.x, 4.6 Jan 9, 2024
@pepov pepov modified the milestones: 4.6, 4.7 Mar 28, 2024
@pepov pepov modified the milestones: 4.7, 4.x Jun 6, 2024
@pepov pepov removed this from the 4.x milestone Oct 7, 2024
@kube-logging kube-logging deleted a comment from stale bot Nov 27, 2024
@kube-logging kube-logging deleted a comment from stale bot Nov 27, 2024
@kube-logging kube-logging deleted a comment from stale bot Nov 27, 2024
@csatib02 csatib02 added good first issue Good for newcomers go Pull requests that update Go code labels Nov 29, 2024
@csatib02 csatib02 added this to the Misc/Other milestone Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working go Pull requests that update Go code good first issue Good for newcomers pinned
Projects
Status: No status
Development

No branches or pull requests

3 participants