Add lazyfs support for arm64 robustness workflow #16392
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.
Recently in #14691 we introduced support for lazyfs for nightly
amd64
robustness tests. Witharm64
at tier1 we need to ensurearm64
nightlies also support lazyfs.This was a little more complicated as our
arm64
nightlies run in containers for better isolation on our self hosted runners. In order to mount the lazyfs fuse based filesystem inside a container we need to run a privileged container to ensure the fuse device is passed through and mountable.This pull request is a pre-requisite before wider adoption of containers for etcd workflows can be progressed under #15956.
The good news is once this pull request merges we will be able to combine
robustness-template-arm64.yaml
withrobustness-template.yaml
and go back down to one workflow template for all robustness workflows.