-
Notifications
You must be signed in to change notification settings - Fork 179
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
Collect related objects for ScyllaClusters and ScyllaDBMonitorings in must-gather #1855
Collect related objects for ScyllaClusters and ScyllaDBMonitorings in must-gather #1855
Conversation
00d0a56
to
5c354ce
Compare
#1694 (comment) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
two comments, rest lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
/assign zimnx
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rzetelskik, tnozicka, zimnx The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
#1900 |
master moved / images issue |
/retest |
same manager flake |
@tnozicka: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
and once again #1694 (comment) |
Description of your changes:
This PR adds support for collecting related resources for ScyllaClusters and ScyllaDBMonitorings. Because not all resources are connected through ownerReferences we dump the same namespace and don't filter the objects. Some examples of where ownerRefs wouldn't works are
Services
,Endpoints
or other objects that don't have a direct relationship but affect say firewall rules (like NetworkPolicy). In the end, dumping all the objects in the same namespace seems like the best path.Which issue is resolved by this Pull Request:
Resolves #1568