Making kamel CLI 90% faster on remote clusters #940
Merged
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.
Fix #792
Latest released version:
With this change:
I.e. from 16 seconds to just ~ 2 seconds.
This is fast because it does not initialize all kubernetes custom resources available in the cluster (~50 on a standard OpenShift installation) but focuses on the 5 resource groups that our CLI needs.
Only drawback is that we should remember to sync the set of allowed API groups (you get a unknown-resource error in case you use a new group from the CLI client).
Release Note