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
Move CSIDriver checks from NewMounter to SetUpAt #113306
Conversation
The checks need to get CSIDriver from the API server and the API server may not be the case when NewMounter is called during volume reconstruction.
@jsafrane: 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. |
/sig storage |
getFSGroupPolicy needs to get CSIDriver from the API server, which may not be available during volume reconstruction at kubelet startup.
9b1242a
to
483fd45
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jsafrane, msau42 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 |
What type of PR is this?
/kind feature
What this PR does / why we need it:
In kubernetes/enhancements#3548,
NewMounter
may be called when kubelet does not yet have a connection to the API server. Therefore move all checks that need CSIDriver instance toSetUpAt
.There are two commits, each moving one check.
Which issue(s) this PR fixes:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: