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
volume: FeatureGate access to GetHostIDsForPod() #111693
volume: FeatureGate access to GetHostIDsForPod() #111693
Conversation
@rata: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
After the userns PR got merged: kubernetes#111090 gnufied decided it might be safer if we feature gate this part of the code, due to the kubelet volume host type assertion. That is a great catch and this patch just moves the code inside the feature gate if. Signed-off-by: Rodrigo Campos <rodrigoca@microsoft.com>
43904b7
to
4267f2e
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gnufied, rata 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 |
@kubernetes/sig-release can we get this into 1.25 milestone? See PR description for reasons :) |
/kind bug |
/milestone v1.25 |
After the userns PR got merged:
#111090
@gnufied decided it might be safer if we feature gate this part of the
code, due to the kubelet volume host type assertion.
That is a great catch and this patch just moves the code inside the
feature gate if.
Signed-off-by: Rodrigo Campos rodrigoca@microsoft.com
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
We decided with @gnufied from sig-storage that is better to feature-gate this part of the code, to minimize possible impact of the new userns feature.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
We want to merge this for 1.25, either as part of the exception granted (https://groups.google.com/g/kubernetes-sig-release/c/ASWlhA-tIxE) or as a bug fix.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: