-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Open
Labels
lead-opted-inDenotes that an issue has been opted in to a releaseDenotes that an issue has been opted in to a releasesig/authCategorizes an issue or PR as relevant to SIG Auth.Categorizes an issue or PR as relevant to SIG Auth.sig/nodeCategorizes an issue or PR as relevant to SIG Node.Categorizes an issue or PR as relevant to SIG Node.sig/storageCategorizes an issue or PR as relevant to SIG Storage.Categorizes an issue or PR as relevant to SIG Storage.stage/alphaDenotes an issue tracking an enhancement targeted for Alpha statusDenotes an issue tracking an enhancement targeted for Alpha statustracked/noDenotes an enhancement issue is NOT actively being tracked by the Release TeamDenotes an enhancement issue is NOT actively being tracked by the Release Team
Description
Enhancement Description
- One-line enhancement description (can be used as a release note): Add stickyBit support for emptydir volumes
- Kubernetes Enhancement Proposal: Add stickyBit support for emptydir kubernetes#130277
- Discussion Link: Set Sticky bit for
emptyDirfolders kubernetes#110835 - PRs by stage and milestone:
- Alpha - v1.xx
- KEP (
k/enhancements) update PR(s): Add KEP-5502 for EmptyDir volume sticky bit support #5857 - Code (
k/k) update PR(s): Add stickyBit support for emptydir kubernetes#130277 - Docs (
k/website) update PR(s):
- KEP (
- Alpha - v1.xx
Why is this relevant?
Many containerized Ruby applications require /tmp directories with the sticky bit set. Without it, emptyDir cannot be reliably used for temporary storage. This forces applications to fall back to ephemeral volumes (complex to manage) or RWX volumes (not well supported across providers).
Allowing emptyDir volumes to be mounted with the sticky bit set would greatly reduce operational complexity for such workloads.
Proposal
Instead of allowing arbitrary permissions (which could introduce risk), extend the spec to ensure the sticky bit can be applied to emptyDir regardless of permission settings. This provides a stable and predictable mechanism, even if future changes further restrict permissions.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
lead-opted-inDenotes that an issue has been opted in to a releaseDenotes that an issue has been opted in to a releasesig/authCategorizes an issue or PR as relevant to SIG Auth.Categorizes an issue or PR as relevant to SIG Auth.sig/nodeCategorizes an issue or PR as relevant to SIG Node.Categorizes an issue or PR as relevant to SIG Node.sig/storageCategorizes an issue or PR as relevant to SIG Storage.Categorizes an issue or PR as relevant to SIG Storage.stage/alphaDenotes an issue tracking an enhancement targeted for Alpha statusDenotes an issue tracking an enhancement targeted for Alpha statustracked/noDenotes an enhancement issue is NOT actively being tracked by the Release TeamDenotes an enhancement issue is NOT actively being tracked by the Release Team
Type
Projects
Status
KEP Backlog
Status
Removed from Milestone