Closed davidkarlsen closed 8 months ago
the driver would search Standard_ZRS account first, from below info, it's got a Premium_LRS account, @davidkarlsen have you got a wrong account?
Performance
:
Premium
Replication
:
Locally-redundant storage (LRS)
Account kind
:
FileStorage
Provisioning state
:
Succeeded
Created
:
09/08/2023, 12:19:25
But the driver should search for existing accounts, use one if a match is there, else create a new one? https://docs.openshift.com/container-platform/4.12/storage/container_storage_interface/persistent-storage-csi-azure.html#persistent-storage-csi-azure-disk-sc-zrs_persistent-storage-csi-azure At least that is what happened for my other LRS disks.
I see where the problem is, since NFS protocol only supports Premium storage, it would enforce to use Premium_LRS
if you are using standard storage
exactly - wouldn't it make sens to raise an error for this - rather than silently provisioning another sku type?
unfortunately that's the way now, if we raise error now, it may break existing users. if you set "skuName: Premium_ZRS", it should work.
Just ran into this issue. I would say it is pretty much unacceptable to keep it this way as it may lead to unrecoverable data loss if people expect this to be zone redundant.
Also sounds like a huge logic error in the code..
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
I will work out a PR to raise error with NFS + Standard account combination.
What happened:
Requesting a Standard_ZRS sku share will silently create a Premium_LRS instead
What you expected to happen: Fail if not supported, create a Standard_ZRS if supported.
How to reproduce it: See yamls below. Go into portal, observe:
Anything else we need to know?:
Environment: sc:
pvc:
kubectl version
): 1.25.12uname -a
): 4.18.0-372.73.1.el8_6.x86_64