You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ChristianZaccaria
changed the title
Enhance/optimise current implementation of processing newly added Job Frameworks.
[Discussion] Enhance/optimise current implementation of processing newly added Job Frameworks.
Aug 15, 2024
Just a little bit of motivation, this will allow us:
reduce the amount of logging for not installed CRDs
shorten the time for the API to be ready - currently due to the exponential backoff the detection of API is likely to take 2min (max period). if we start active polling after the CRD is installed the REST mapper will be detected quickly.
I think an integration test can be added even to the current mechanism, so I think it makes sense to keep #3015 open
This is a follow-up issue to PR #2574: Start JobFramework controller and webhook on new CRDs availability.
What would you like to be added:
Enhance/optimise current design and implementation of #2574
Why is this needed:
waitForAPI()
once the CRD is registered (wait either by controller or watcher on CRD type).apiextensions
. Once we discover a new CRD, then we start waiting for the restmapper to be filled.Completion requirements:
This enhancement requires the following artifacts:
The artifacts should be linked in subsequent comments.
The text was updated successfully, but these errors were encountered: