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
fix azure disk translation issue due to lower case managed
kind
#103439
fix azure disk translation issue due to lower case managed
kind
#103439
Conversation
/kind bug |
/lgtm |
if azureSource.Kind != nil { | ||
pv.Spec.PersistentVolumeSource.CSI.VolumeAttributes[azureDiskKind] = string(*azureSource.Kind) | ||
} | ||
pv.Spec.PersistentVolumeSource.CSI.VolumeAttributes[azureDiskKind] = managed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can something not managed be specified?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
since CSI driver only supports managed, we can only support managed
in csi migration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we make the CSI driver case insensitive?
In theory, we could fix it in volume validation, while since this issue only exists in csi migration, may be not necessary now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happens if someone is using a volume that is unmanaged with CSI migration?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happens if someone is using a volume that is unmanaged with CSI migration?
it's not supported, volume would be in unattached state forever. unmanaged disk is actually deprecated in Azure, if user still wants to use unmanaged disk, they need to turn off csi migration for disk.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can a user use unmanaged disks with in-tree driver today? If so, we may need to also send a deprecation notice for this.
Also, should we return an error if the kind is not supported?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
already added the error code and depreciation notice in doc notes if kind is not supported.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, can you also clarify, is there any documentation we can point to users on how to migrate their disks from unmanaged to managed?
/retest |
/retest |
2 similar comments
/retest |
/retest |
/assign |
@msau42 could you approve this PR? thanks. |
@andyzhangx I think deprecation warning should really say, shared and dedicated types are deprecated for azure disk volumes. The CSI migration or not condition is implicit. |
changed to
|
@andyzhangx I think @gnufied's suggestion is to deprecate the support for in-tree plugin too. Can we also provide a link to tell users how to migrate to managed disks? |
@msau42 added a link about how to migrate to managed disks. The in-tree plugin is already in maintainace mode and deprecated soon, I think that's a common sense.
|
@andyzhangx I think there is a subtle distinction. The in-tree driver is deprecated, however the in-tree API is still supported. So since this is something users used to be able to specify in the API, and will not be able to in the future, it should be called out. |
@msau42 I added sth. here, is that ok?
|
/lgtm |
/approve Thanks! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andyzhangx, 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 |
/milestone v1.22 |
…103439-upstream-release-1.22 Automated cherry pick of #103439: fix azure disk translation issue
What type of PR is this?
/kind bug
What this PR does / why we need it:
fix azure disk translation issue due to lower case
managed
kindWhich issue(s) this PR fixes:
Fixes #103433
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: