CSI compatibility mode#175
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
…esource Signed-off-by: Niclas Schad <niclas.schad@stackit.cloud>
Signed-off-by: Niclas Schad <niclas.schad@stackit.cloud>
Signed-off-by: Niclas Schad <niclas.schad@stackit.cloud>
Signed-off-by: Niclas Schad <niclas.schad@stackit.cloud>
Signed-off-by: Niclas Schad <niclas.schad@stackit.cloud>
Signed-off-by: Niclas Schad <niclas.schad@stackit.cloud>
Signed-off-by: Niclas Schad <niclas.schad@stackit.cloud>
Signed-off-by: Niclas Schad <niclas.schad@stackit.cloud>
Signed-off-by: Niclas Schad <niclas.schad@stackit.cloud>
4fa0ce5 to
c923b5d
Compare
|
/test pull-gardener-extension-provider-stackit-verify |
|
/test pull-gardener-extension-provider-stackit-verify |
|
/test pull-gardener-extension-provider-stackit-verify |
|
/hold until stackitcloud/cloud-provider-stackit#161 is merged |
…sion Signed-off-by: Niclas Schad <niclas.schad@stackit.cloud>
…ifferent driverName Signed-off-by: Niclas Schad <niclas.schad@stackit.cloud>
Signed-off-by: Niclas Schad <niclas.schad@stackit.cloud>
Signed-off-by: Niclas Schad <niclas.schad@stackit.cloud>
…y mode Signed-off-by: Niclas Schad <niclas.schad@stackit.cloud>
compatibility driver
ManagedResource CRs are deployed
|
PR needs rebase. DetailsInstructions 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-sigs/prow repository. |
| @@ -1,3 +1,4 @@ | |||
| {{- if not .Values.csi.enableCompatibilityMode }} | |||
There was a problem hiding this comment.
Why do we dont deploy the PodDisruptionBudget when enable the CompatibilityMode
There was a problem hiding this comment.
@dergeberl We only need one snapshot controller per cluster. It would just be duplicated doing nothing.
| @@ -1,4 +1,4 @@ | |||
| --- | |||
| {{- if not .Values.csi.enableCompatibilityMode }} | |||
There was a problem hiding this comment.
Why do we dont deploy the VerticalPodAutoscaler when enable the CompatibilityMode
There was a problem hiding this comment.
Same as above. One snapshot-controller is suffice.
| @@ -1,3 +1,4 @@ | |||
| {{- if not .Values.csi.enableCompatibilityMode }} | |||
There was a problem hiding this comment.
This is not needed as the snapshot-controller dont use the driverName right? Snapshots can be still created for both drivernames?
There was a problem hiding this comment.
Yes, correct. The leader of the controller is also hard-coded so it wouldn't even bring you anything if you have multiple controllers running.
| annotations: | ||
| checksum/configmap-cloud-provider-config: {{ include (print $.Template.BasePath "/configmap.yaml") . | sha256sum }} | ||
| node.gardener.cloud/wait-for-csi-node-stackit: block-storage.csi.stackit.cloud | ||
| {{- if eq .Values.driverName "cinder.csi.openstack.org" }} |
There was a problem hiding this comment.
We could use the enableCompatibilityMode instead if the driver here
| {{- if eq .Values.driverName "cinder.csi.openstack.org" }} | |
| {{- if .Values.csi.enableCompatibilityMode }} |
There was a problem hiding this comment.
It is then also needed to switch the annotations in the if/else
| Name string `json:"name"` | ||
| CompatibilityMode string `json:"compatibilityMode,omitempty"` |
There was a problem hiding this comment.
Can we add a description/comment here what this fields are and what the default is?
|
@ftl: The following tests failed, say
Full PR test history. Your PR dashboard. Command help for this repository. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
How to categorize this PR?
/kind enhancement
What this PR does / why we need it:
This change allows to deploy two separate instances of the STACKIT CSI driver, on in "normal" mode, and the second one in "compatibility" mode. This is part of the migration from cinder to the STACKIT CSI driver.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
This change requires the enhancement stackitcloud/cloud-provider-stackit#161 to be available in the cloud-provider-stackit CSI driver plugin.
Breaking changes: