Skip to content
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

Merged
merged 2 commits into from
Oct 31, 2022
Merged

Refactor validation for csiConfig #2430

merged 2 commits into from
Oct 31, 2022

Conversation

xmudrii
Copy link
Member

@xmudrii xmudrii commented Oct 28, 2022

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/comment csiConfig 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:

- `.cloudProvider.csiConfig` is now a mandatory field for vSphere clusters using the external cloud provider (`.cloudProvider.external: true`)
- `.cloudProvider.csiConfig` can be specified even if the in-tree provider is used, but the provided CSIConfig is ignored in such cases (a warning about this is printed)

Documentation:

NONE

Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
@xmudrii xmudrii requested a review from kron4eg October 28, 2022 17:56
@kubermatic-bot kubermatic-bot added kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API release-note Denotes a PR that will be considered when it comes time to generate release notes. docs/none Denotes a PR that doesn't need documentation (changes). dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Oct 28, 2022
@xmudrii
Copy link
Member Author

xmudrii commented Oct 28, 2022

/retest

@xmudrii xmudrii added the backport-needed Denotes a PR or issue that has not been fully backported. label Oct 30, 2022
@kron4eg
Copy link
Member

kron4eg commented Oct 31, 2022

/approve
/lgtm

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Oct 31, 2022
@kubermatic-bot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: c7ddded7f9e7226b47cfed0c9850ca5f0fa43b6c

@kubermatic-bot kubermatic-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 31, 2022
@kubermatic-bot kubermatic-bot merged commit a5c2cf4 into main Oct 31, 2022
@kubermatic-bot kubermatic-bot added this to the KubeOne 1.6 milestone Oct 31, 2022
@kubermatic-bot kubermatic-bot deleted the csiconfig-validation branch October 31, 2022 09:24
@xmudrii
Copy link
Member Author

xmudrii commented Nov 7, 2022

/cherrypick release/v1.5

@kubermatic-bot
Copy link
Contributor

@xmudrii: new pull request created: #2447

In response to this:

/cherrypick release/v1.5

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.

@xmudrii xmudrii added backport-complete Denotes a PR or issue which has been fully backported to all required release branches. and removed backport-needed Denotes a PR or issue that has not been fully backported. labels Nov 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-complete Denotes a PR or issue which has been fully backported to all required release branches. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. docs/none Denotes a PR that doesn't need documentation (changes). kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants