Document clearly that fsGroup does not apply to hostPath volumes - #57409
Document clearly that fsGroup does not apply to hostPath volumes#57409IanEff wants to merge 1 commit into
Conversation
Signed-off-by: Ian Furst <ian.furst@gmail.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Welcome @IanEff! |
|
/sig storage |
|
/sig docs |
|
/kind documentation |
|
@wilmerdooley Would you mind taking a quick look at this, and see whether I captured everything from the comments in the underlying issue, kubernetes/kubernetes#138411? |
Description
fsGroupandfsGroupChangePolicysilently have no effect onhostPathvolumes-- the kubelet never chowns a host directory, unlike managed volume types. This is documented for ephemeral volume types, but not forhostPath, so users hit it by trial and error.This adds a caution o the
hostPathvolume type docs and a note tot he security condext docs'fsGroupdiscussion. Both point the user tolocalPersistentVolumes as thefsGroup-managed alternative.Issue
Ref kubernetes/kubernetes#138411
This is docs-only clarification of expected behavior. See the triage from @wilmerdooley on that issue.