New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable NewVolumeManagerReconstruction and SELinuxMountReadWriteOncePod feature gate #117751
Disable NewVolumeManagerReconstruction and SELinuxMountReadWriteOncePod feature gate #117751
Conversation
/approve |
LGTM label has been added. Git tree hash: e42e1e231103dd5fe6cfe19b43fc3d71c8e3bf96
|
/triage accepted |
/hold for storage ack |
@jsafrane if we disable this feature gate, should we also disable SELinuxMount feature gate and hold off on the backport of #116134 (comment)? |
f629730
to
d0529d0
Compare
/lgtm |
LGTM label has been added. Git tree hash: 634a420c746cb0ff3a0d4afa4b0f340b4b262738
|
d0529d0
to
7a3b9f8
Compare
repushed with a comment linking to the issue beside the SELinuxMountReadWriteOncePod feature gate |
/hold cancel |
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
grrr... unit tests assuming the feature gate is on, fixing... |
7a3b9f8
to
c8c7cd2
Compare
fixed unit test and added comprehensive unit tests of update validation with the feature enabled/disabled |
@liggitt still failing those unit tests |
c8c7cd2
to
e807a6a
Compare
was a separate package, fixed |
/lgtm |
LGTM label has been added. Git tree hash: 07120f02c0d523b15f9f4d80577ef3e42ff47ae9
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, liggitt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…751-upstream-release-1.27 Automated cherry pick of #117751: Disable NewVolumeManagerReconstruction / SELinuxMountReadWriteOncePod feature gates
What type of PR is this?
/kind bug
/kind regression
What this PR does / why we need it:
Reverts the NewVolumeManagerReconstruction feature gate to disabled until #117745 is root-caused and resolved
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/sig storage
/assign @msau42 @jsafrane