This repository has been archived by the owner on Nov 9, 2022. It is now read-only.
Switch to DynamicRESTMapper for target client #93
Assignees
Labels
area/quality
Output qualification (tests, checks, scans, automation in general, etc.) related
area/scalability
Scalability related
kind/cleanup
Something that is not needed anymore and can be cleaned up
kind/enhancement
Enhancement, improvement, extension
priority/3
Priority (lower number equals higher priority)
Comments
gardener-robot
added
area/quality
|
/assign |
gardener-robot
added
the
priority/3
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
How to categorize this issue?
/area scalability
/kind cleanup
/priority normal
What would you like to be added:
With the recent improvements in controller-runtime (kubernetes-sigs/controller-runtime#1151), we can/should replace the
DeferredDiscoveryRESTMapperby aDynamicRESTMapperto avoid explicit rediscovery.https://github.com/gardener/gardener-resource-manager/blob/827ae66273760c834b2dcf34459d8cf2fca5a387/pkg/controller/managedresources/controller.go#L463-L468
This way, grm immediately rediscovers resources if some of them are not known (yet), so that no extra reconciliation is needed.
It will still adhere to the specified rate limits, so we don't do unnecessary extraneous discovery calls (even across managed resources - which wasn't the case before).
The text was updated successfully, but these errors were encountered: