-
Notifications
You must be signed in to change notification settings - Fork 101
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
EndpointSlice resources tracked by Graph #1432
EndpointSlice resources tracked by Graph #1432
Conversation
Had a few questions / checks on the logic of the changes I would like to have looked at before completing the changes and adding tests, Thanks! |
dbb211a
to
583738a
Compare
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.
Really nice job, @bjee19! This makes our code much simpler 🚀
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.
👍
c129995
to
635178b
Compare
Proposed changes
Problem: EndpointSlice resources are currently being tracked by the relationship capturer, but to reduce the number of components we would like to track the resources in the Graph.
Solution: Enable Graph to track EndpointSlice resources and Services. In addition, this PR refactors
backend_refs
to store theNamespacedName
of a Service and aServicePort
instead of the actual Service. This is done to track non-existing referenced services. Also, refactors and removes thealwaysTruePredicate
introduced in this PR. Removes RelationshipCapturer.Testing: Wrote new unit tests and refactored existing ones.
Closes #1264
Checklist
Before creating a PR, run through this checklist and mark each as complete.