Skip to content
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

Caching the version per cluster #26

Open
qcloutier-sonrai opened this issue May 17, 2022 · 1 comment
Open

Caching the version per cluster #26

qcloutier-sonrai opened this issue May 17, 2022 · 1 comment

Comments

@qcloutier-sonrai
Copy link

From my understanding, kuberlr queries the remote cluster for its version every time kubectl is invoked. This is way too slow to be practical -- it takes several seconds to get anything from, for example, EKS. Even working with a local cluster like Rancher Desktop has a noticeable slowdown.

It would be nice if kuberlr would automatically cache the version for each cluster it is used with, and refer to it when deciding which version of kubectl to use. If more than a day (or some other configurable amount of time) has passed between the last time a version was cached, it would only then make the extra query for the version.

@mattfarina
Copy link
Contributor

There are some situations where kuberlr is used (e.g., Rancher Desktop) where the version can change more often. Such as when you're testing workloads under Kubernetes version upgrades. When caching is used there should be a way to handle this well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants