-
-
Notifications
You must be signed in to change notification settings - Fork 303
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
Support discovery cache in local ~/.kube/cache/discovery directory like kubectl #1021
Comments
Yeah, I think this makes sense. It's probably not something we should have on by default (since we are more a client-go equivalent than a kubectl equivalent), but we can pass in a cache location like Some questions;
|
I agree. Indeed, there are many unclear points, and we need more time to figure out. |
I see that kubectl uses more details: |
Can also see that this is wrapped up in a A long timeout makes sense for this type of cache, but if a controller is mutating apis it can also make sense to expose the invalidate call. |
Yeah, it looks like an available solution. But still have many details not reach a consensus, like cache file format. I am going to implement it first and make a pr. By that time, let's explore further. |
Keep the same format for Interoperability would be great. |
Would you like to work on this feature?
No response
What problem are you trying to solve?
Since the API resources are not changing frequently, we do not need to discover the resource which has been found in the previous API query.
Describe the solution you'd like
Cache the discovery in
~/.kube/cache/discovery
like what kubectl does.Describe alternatives you've considered
No alternatives
Documentation, Adoption, Migration Strategy
No response
Target crate for feature
kube-client
The text was updated successfully, but these errors were encountered: