Ensure discovery cache can be written by client-go in the kubeappsapis service #6128
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
Gives permission for the running process to write the k8s discovery cache when kubeapps-apis first communicates with the k8s api server.
This doesn't appear to affect users, but may be contributing to memory usage and potentially restarts.
Before this change, after deploying an app, the following would appear in the kubeapps-apis logs:
The client appears to work fine without a cache, but will be doing unnecessary work with each deploy (and we did in the past investigate an issue where memory was being consumed on each deploy resulting in kubeapps-apis restarts).
With this change, the above errors are no longer seen, and the cache can be verified with:
Benefits
Better resource usage and possibly less memory and restarts in some environments.
Possible drawbacks
Applicable issues
Additional information