New K8s clients provider for Kapp and Resources plugins #5405
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the change
3rd and final PR related to K8s Go clients optimization (#5358 and #5379)
In this one, Kapp and Resources plugins code have been refactored. Previously used client getter has been removed.
Now all plugins use the same client getter/provider.
Instead of creating two clients most of the times and ignoring one:
now each one can be created independently:
Benefits
Possible drawbacks
N/A
Applicable issues
Additional information
There is still lag when creating a dynamic client and using
pinniped-proxy
. This might be related to K8s APIs throttling from Rust.