Mountpoint chown recursive now optional #758
Merged
Conversation
This file contains 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
g-foster2020
previously approved these changes
Mar 23, 2023
kierenevans
force-pushed
the
mountpoint-chown-recursive-optional
branch
from
d8550b7 to
b1e8826
Compare
andytson-inviqa
previously approved these changes
Mar 24, 2023
When there are a large amount of files, the recursive chown on some filesystems causes a big delay in allowing the pod to start up.
kierenevans
force-pushed
the
mountpoint-chown-recursive-optional
branch
from
b1e8826 to
10e9a01
Compare
andytson-inviqa
approved these changes
Mar 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 there are a large amount of files, the recursive chown on some filesystems causes a big delay in allowing the pod to start up.
The recursive chown on NFS is ignored due to user management largely being ignored, but some filesystems do offer the ability to change the user.
The intention of this was to change the owner of the mountpoint rather than the owner of the files within the mountpoint, as hopefully the files within are already owned correctly.