csi-azuredisk-driver crashes... when --set cloud=AzureStackCloud

[chris8205]

What happened:

Pods are crashing when using --set cloud=AzureStackCloud

Maybe there is a config step missing in the docs??

How to reproduce it:

helm upgrade -i azuredisk-csi-driver azuredisk-csi-driver/azuredisk-csi-driver --version 2.0.0-beta.6 --namespace kube-system --set cloud=AzureStackCloud --set node.livenessProbe.healthPort=39705

Environment:

AzureStack HCI 23Hx

K8s Version: 1.28

ErrorLOG:

I0905 14:20:44.216463 1 main.go:250] set up prometheus server on [::]:29605
W0905 14:20:44.216526 1 azuredisk_v2.go:147] Using DriverV2
I0905 14:20:44.216744 1 azuredisk_v2.go:195]
DRIVER INFORMATION:

Build Date: "2022-08-12T16:48:11Z"
Compiler: gc
Driver Name: disk.csi.azure.com
Driver Version: v2.0.0-beta.6
Git Commit: d0153ef
Go Version: go1.18.5
Platform: linux/amd64
Topology Key: topology.disk.csi.azure.com/zone

Streaming logs below:
I0905 14:20:44.218022 1 reflector.go:219] Starting reflector *v1.Node (30s) from k8s.io/client-go/informers/factory.go:134
I0905 14:20:44.218060 1 reflector.go:255] Listing and watching *v1.Node from k8s.io/client-go/informers/factory.go:134
I0905 14:20:44.318518 1 shared_informer.go:285] caches populated
I0905 14:20:44.319478 1 reflector.go:219] Starting reflector *v1beta2.AzDriverNode (30s) from sigs.k8s.io/azuredisk-csi-driver/pkg/apis/client/informers/externalversions/factory.go:117
I0905 14:20:44.319534 1 reflector.go:255] Listing and watching *v1beta2.AzDriverNode from sigs.k8s.io/azuredisk-csi-driver/pkg/apis/client/informers/externalversions/factory.go:117
I0905 14:20:44.319646 1 reflector.go:219] Starting reflector *v1beta2.AzVolumeAttachment (30s) from sigs.k8s.io/azuredisk-csi-driver/pkg/apis/client/informers/externalversions/factory.go:117
I0905 14:20:44.319691 1 reflector.go:255] Listing and watching *v1beta2.AzVolumeAttachment from sigs.k8s.io/azuredisk-csi-driver/pkg/apis/client/informers/externalversions/factory.go:117
I0905 14:20:44.320298 1 reflector.go:219] Starting reflector *v1beta2.AzVolume (30s) from sigs.k8s.io/azuredisk-csi-driver/pkg/apis/client/informers/externalversions/factory.go:117
I0905 14:20:44.320331 1 reflector.go:255] Listing and watching *v1beta2.AzVolume from sigs.k8s.io/azuredisk-csi-driver/pkg/apis/client/informers/externalversions/factory.go:117
I0905 14:20:44.419262 1 shared_informer.go:285] caches populated
I0905 14:20:44.419506 1 azuredisk_v2.go:226] driver userAgent: disk.csi.azure.com/v2.0.0-beta.6 OSS-helm
I0905 14:20:44.419606 1 azure_disk_utils.go:540] reading cloud config from secret kube-system/azure-cloud-provider
I0905 14:20:44.425279 1 azure_disk_utils.go:547] InitializeCloudFromSecret: failed to get cloud config from secret kube-system/azure-cloud-provider: failed to get secret kube-system/azure-cloud-provider: secrets "azure-cloud-provider" not found
I0905 14:20:44.425324 1 azure_disk_utils.go:552] could not read cloud config from secret kube-system/azure-cloud-provider
I0905 14:20:44.425344 1 azure_disk_utils.go:562] use default AZURE_CREDENTIAL_FILE env var: /etc/kubernetes/azure.json
W0905 14:20:44.425409 1 azure_disk_utils.go:567] load azure config from file(/etc/kubernetes/azure.json) failed with open /etc/kubernetes/azure.json: no such file or directory
I0905 14:20:44.425436 1 azure_disk_utils.go:579] no cloud config provided, error: failed to get secret kube-system/azure-cloud-provider: secrets "azure-cloud-provider" not found, driver will run without cloud config
F0905 14:20:44.425454 1 cloudprovisioner.go:108] failed to get Azure Cloud Provider, error:

[andyzhangx]

are you running the csi driver on Azure stack node? follow this guide to set cloud provider config: https://github.com/kubernetes-sigs/azuredisk-csi-driver?tab=readme-ov-file#prerequisite

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale