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
Remove option to disable kube caching #5599
Comments
Rather than blocking making the cache mandatory on refactoring all the backend unit tests, @israel-hdez had the idea of removing the external config option while keeping the internal cfg option that the unit tests can still set. I think this is a better way forward and we should do this while the test refactoring is on-going. @israel-hdez I'm assigning you to this task but feel free to unassign yourself or assign someone else. |
This small change will prevent reading (unmarshalling) the kubernetes_config.cache_enabled configuration from a YAML file (i.e. from a Kubernetes ConfigMap). This effectively makes it impossible to disable Kiali's kube cache via the usual configuration mechanism. This will allow to write new code under the assumption that the kube cache is always enabled (i.e. no more if/else conditionals around this configuration variable). The kube cache can still be disabled programmatically. This will allow to gradually update existing code to stop relying on the removed configuration (most notably, unit tests need to be adapted). Related kiali#5599
The adaptation moves from using mocks to using a fake client. This allows for starting a cache where the underlying client is a fake, making it possible to allow the code to use "caching" as with the real client. Related kiali#5599
Transferring this issue to @leandroberetta as the new Ωwner. |
The gist of this work is just removing |
Caching has been enabled by default for some time now. This issue is to remove the option to disable kube caching. Kiali may still query the kube api directly in some cases but will largely rely on the local cache. Some supported kube types are not currently cached like
CronJob
but these should be added as well.This is a followup to #5319 and #4678.
The text was updated successfully, but these errors were encountered: