If I understand it correctly, alibaba-disk-csi-driver-operator should provide the group ID in csi-disk StorageClass: parameters: resourceGroupId: <the resource group from install-config.yaml>
It works if we adding sc.parameters.resourceGroupId in the storageclass. Here I'm not sure if our operator should do this (adding resourceGroupId in preset sc) or CSI Driver should default create volume in the same resource group with cluster.
... and the resource group is part of infrastructure.status: apiVersion: config.openshift.io/v1 kind: Infrastructure metadata: name: cluster spec: cloudConfig: key: config name: cloud-provider-config platformSpec: type: AlibabaCloud status: [...] platform: AlibabaCloud platformStatus: alibabaCloud: region: us-east-1 resourceGroupID: rg-acfnxrgr6qtm3mq type: AlibabaCloud
> Here I'm not sure if our operator should do this (adding resourceGroupId in preset sc) or CSI Driver should default create volume > in the same resource group with cluster. I think the operator should set the resource group in the default StorageClass, to have all cluster resources together.
> Here the "resourceGroupID" should be "resourceGroupId" inside default sc. Good catch! I should not have tested in the default resource group!
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069