-
Notifications
You must be signed in to change notification settings - Fork 233
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
Refactor validation for csiConfig #2430
Conversation
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
/retest |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kron4eg 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 |
LGTM label has been added. Git tree hash: c7ddded7f9e7226b47cfed0c9850ca5f0fa43b6c
|
/cherrypick release/v1.5 |
@xmudrii: new pull request created: #2447 In response to this:
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. |
What this PR does / why we need it:
After discussing internally with @kron4eg, we decided to make it possible to provide
.cloudProvider.csiConfig
even if the in-tree provider is used. This needed to make implementing E2E tests easier/possible, as well as, to make it easier to test vSphere integration manually (e.g. you don't need to delete/commentcsiConfig
each time you want to test something).In such cases when CSIConfig is used with the in-tree provider, the CSIConfig is ignored and a warning about this is printed.
Additionally, CSIConfig is now a mandatory field for vSphere if external is enabled. This wasn't the case before, however, if you don't provide CSIConfig, vSphere CSI will crashloop, resulting in a non-functional cluster.
What type of PR is this?
/kind api-change
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: