This repository was archived by the owner on Jun 5, 2025. It is now read-only.
Adding an emptyDir
to kubernetes deployment
#380
Merged
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.
This should resolve the out-of-disk problems reported in #379
Mounting an emptyDir volume for the Buildkite working directory should remove the disk space limitations from Kubernetes. So now it's only limited by the physical disc space available to the VM.
I did not check in detail but it looks like the ccache folder is also below
/var/lib/buildkite-agent
so that should be covered as well.It might cause issues with the permissions. In that case we would probably need to change the permissions after the volume is mounted. So that would have to go into the
entrypoint.sh
script.@metaflow Can you please review the change? I did not dare to apply it so far...