enhancements
enhancements copied to clipboard
KEP 1710: Update SELinux mount ReadWriteOnce optimization for 1.26
Update "Speed up recursive SELinux label change" for Kubernetes 1.26
-
Issue link: #1710
-
Updated the checkboxes at the beginning with the current state.
-
Added metrics.
-
Added details about volume reconstruction refactoring.
The feature stays in alpha in 1.26.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jsafrane
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~keps/sig-storage/OWNERS~~ [jsafrane]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Not sure if it's needed, the feature was alpha in 1.25 and stays so in 1.26 /label lead-opted-in
/retitle KEP 1710: Update SELinux mount ReadWriteOnce optimization for 1.26
/assign @gnufied @jingxu97 to review reconstruction design changes
I am linking all volume reconstruction PRs to this enhancement update - I am trying to make as small and independent PRs as possible.
I know we're changing this as part of the SELinux work but I wonder if it's worth having a separate doc just for reconstruction in general. There are other issues that would be great to fix such as reconstructing global mounts, and supporting non-mounting csi drivers.
separate doc just for reconstruction in general
That sounds good. Where the document should be? We still have https://github.com/kubernetes/community/tree/master/contributors/devel/sig-storage, but IMO it's not a good place.
separate doc just for reconstruction in general
I opened https://github.com/kubernetes/enhancements/pull/3763
/close in favor of https://github.com/kubernetes/enhancements/pull/3797
@jsafrane: Closed this PR.
In response to this:
/close in favor of https://github.com/kubernetes/enhancements/pull/3797
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.