k3s: Document tuning kubernetes image cache #3230
Merged
+5
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When we aren't using disk on the host for anything else, kubernetes can simply use as much of the disk as it wants for caching images. The default for this is upto 85%. However, since we *do* use the disk for our dind, we want to tune this to take up only half that size. I've already applied this to the 2i2c-hetzner node Follow-up to jupyterhub#3229
Contributor
Author
You can immediately see the effect of this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When we aren't using disk on the host for anything else, kubernetes can simply use as much of the disk as it wants for caching images. The default for this is upto 85%. However, since we do use the disk for our dind, we want to tune this to take up only half that size.
I've already applied this to the 2i2c-hetzner node
Follow-up to #3229