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
Turn CSIMigrationAWS on by default #106098
Turn CSIMigrationAWS on by default #106098
Conversation
/sig storage |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
just that subPath test failing.
details:
|
I ran the test with up-to-date kubelet and csi-proxy and the I ran the test with the in-tree driver (with CSIMigration off) and the test failed as well. So strictly speaking I don't think the failure must block migration since the same bug affects both in-tree and CSI... Details on the bug: The volume never gets detached, so PV never gets deleted, so the test fails. The fix is to take the volume offline, then detach succeeds. AWS official documentation recommends doing this https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ebs-detaching-volume.html#detach but neither the in-tree nor CSI driver do it, instead they just clear the write cache and remove all paths referencing the volume. This works in all other test cases so it's not clear yet why taking the volume offline is necessary only in the CSI issue just filed: kubernetes-sigs/aws-ebs-csi-driver#1116 in either case kernel prints this so I guess it has something to do with how kubelet does the subpath mounts/unmounts and taking disk offline avoids it?
|
/hold cancel My testing is done, there is one failure that represents a bug in in-tree/CSI windows implementation. |
kubernetes-sigs/aws-ebs-csi-driver#1116 seems sufficient to track this, so: /lgtm |
/lgtm |
/milestone v1.23 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: msau42, wongma7 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 |
/triage accepted |
since k8s 1.23 CSIMigrationAWS is turn by default and require installation of AWS EBS CSI driver even if we don't use external ccm (kubernetes/kubernetes#106098) Signed-off-by: Vincent Gramer <vincent@kubermatic.com>
since k8s 1.23 CSIMigrationAWS is turn by default and require installation of AWS EBS CSI driver even if we don't use external ccm (kubernetes/kubernetes#106098) Signed-off-by: Vincent Gramer <vincent@kubermatic.com>
since k8s 1.23 CSIMigrationAWS is turn by default and require installation of AWS EBS CSI driver even if we don't use external ccm (kubernetes/kubernetes#106098) Signed-off-by: Vincent Gramer <vincent@kubermatic.com>
since k8s 1.23 CSIMigrationAWS is turn by default and require installation of AWS EBS CSI driver even if we don't use external ccm (kubernetes/kubernetes#106098) Signed-off-by: Vincent Gramer <vincent@kubermatic.com>
since k8s 1.23 CSIMigrationAWS is turn by default and require installation of AWS EBS CSI driver even if we don't use external ccm (kubernetes/kubernetes#106098) Signed-off-by: Vincent Gramer <vincent@kubermatic.com>
) * refactor: move function MustParseConstraint from pkg/apis/kubeone/validation/validation.go to pkg/semverutil/helper.go Signed-off-by: Vincent Gramer <vincent@kubermatic.com> * AWS: install csi driver if k8s >1.23 even if cloud.external=false since k8s 1.23 CSIMigrationAWS is turn by default and require installation of AWS EBS CSI driver even if we don't use external ccm (kubernetes/kubernetes#106098) Signed-off-by: Vincent Gramer <vincent@kubermatic.com>
What type of PR is this?
/kind feature
What this PR does / why we need it:
Turn the feature on by default.
kubernetes/enhancements#1487
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: