-
Notifications
You must be signed in to change notification settings - Fork 708
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
Remove replica sets #2661
Remove replica sets #2661
Conversation
c9af113
to
2f1d765
Compare
This approach is a little hacky, but is the best we can do without changing the probe, which won't work retroactively. One other option would be changing the probe, and then doing this re-mapping to remove replica sets at |
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.
This is lovely!
I've benchmarked it and kube-controllers is marginally slower, but that is kinda expected.
Ultimately that is the correct way to go, but only once we are sure we won't change our minds about not representing replicasets. I have raised #2662 for this. |
FTR, this PR is part of #2620. |
PS: please make the linter happy |
Use a special kind of selector renderer to elide replica sets from pod nodes and directly reference deployment parents instead. Do the inverse (replace replica sets with pods) during the mapping from pod to deployment. Note we can no longer use renderParents since we're using a non-standard Selector
2f1d765
to
ef2b6f6
Compare
note: though github claims '1 of 2 test passed', it was netlify that was failing, which doesn't even test anything afaict. |
Use a special kind of selector renderer to elide replica sets from pod nodes
and directly reference deployment parents instead.
Do the inverse (replace replica sets with pods) during the mapping from pod to deployment.
Note we can no longer use renderParents since we're using a non-standard Selector