Skip to content

Latest commit

 

History

History
 
 

charts

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Install CSI driver with Helm 3


Prerequisites

Tips

  • schedule controller running on control plane node: --set controller.runOnControlPlane=true
  • set replica of controller as 1: --set controller.replicas=1
  • specify different cloud config secret for the driver:
    • --set controller.cloudConfigSecretName
    • --set controller.cloudConfigSecretNamesapce
    • --set node.cloudConfigSecretName
    • --set node.cloudConfigSecretNamesapce
  • switch to mcr.azk8s.cn repository in Azure China: --set image.baseRepo=mcr.azk8s.cn

Helm Chart Repository Management

add the Helm chart repository

helm repo add azuredisk-csi-driver https://raw.githubusercontent.com/kubernetes-sigs/azuredisk-csi-driver/master/charts

search for all available chart versions

helm search repo -l azuredisk-csi-driver

update the repository

helm repo update azuredisk-csi-driver

Azure Disk CSI Driver V1

install a specific version

helm install azuredisk-csi-driver azuredisk-csi-driver/azuredisk-csi-driver --namespace kube-system --version v1.21.0

install on Azure Stack

helm install azuredisk-csi-driver azuredisk-csi-driver/azuredisk-csi-driver --namespace kube-system --set cloud=AzureStackCloud

install on RedHat/CentOS

helm install azuredisk-csi-driver azuredisk-csi-driver/azuredisk-csi-driver --namespace kube-system --set linux.distro=fedora

install driver with customized driver name, deployment name

only supported from v1.5.0+

  • following example would install a driver with name disk2
helm install azuredisk-csi-driver azuredisk-csi-driver/azuredisk-csi-driver \
  --namespace kube-system \
  --set driver.name="disk2.csi.azure.com" \
  --set controller.name="csi-azuredisk2-controller" \
  --set rbac.name=azuredisk2 \
  --set serviceAccount.controller=csi-azuredisk2-controller-sa \
  --set serviceAccount.node=csi-azuredisk2-node-sa \
  --set linux.dsName=csi-azuredisk2-node \
  --set windows.dsName=csi-azuredisk2-node-win \
  --set node.livenessProbe.healthPort=39705

uninstall CSI driver

helm uninstall azuredisk-csi-driver -n kube-system

latest chart configuration

V1 Parameters

The following table lists the configurable parameters of the latest Azure Disk CSI Driver chart and default values.

Parameter Description Default
driver.name alternative driver name disk.csi.azure.com
driver.customUserAgent custom userAgent ``
driver.userAgentSuffix userAgent suffix OSS-helm
driver.volumeAttachLimit maximum number of attachable volumes per node maximum number is defined according to node instance type by default(-1) -1
driver.azureGoSDKLogLevel Azure go sdk log level ``(no logs), DEBUG, `INFO`, `WARNING`, `ERROR`, etc
feature.enableFSGroupPolicy enable fsGroupPolicy on a k8s 1.20+ cluster true
image.baseRepo base repository of driver images mcr.microsoft.com
image.azuredisk.repository azuredisk-csi-driver docker image /oss/kubernetes-csi/azuredisk-csi
image.azuredisk.tag azuredisk-csi-driver docker image tag ``
image.azuredisk.pullPolicy azuredisk-csi-driver image pull policy IfNotPresent
image.csiProvisioner.repository csi-provisioner docker image /oss/kubernetes-csi/csi-provisioner
image.csiProvisioner.tag csi-provisioner docker image tag v3.2.0
image.csiProvisioner.pullPolicy csi-provisioner image pull policy IfNotPresent
image.csiAttacher.repository csi-attacher docker image /oss/kubernetes-csi/csi-attacher
image.csiAttacher.tag csi-attacher docker image tag v3.5.0
image.csiAttacher.pullPolicy csi-attacher image pull policy IfNotPresent
image.csiResizer.repository csi-resizer docker image /oss/kubernetes-csi/csi-resizer
image.csiResizer.tag csi-resizer docker image tag v1.5.0
image.csiResizer.pullPolicy csi-resizer image pull policy IfNotPresent
image.livenessProbe.repository liveness-probe docker image /oss/kubernetes-csi/livenessprobe
image.livenessProbe.tag liveness-probe docker image tag v2.7.0
image.livenessProbe.pullPolicy liveness-probe image pull policy IfNotPresent
image.nodeDriverRegistrar.repository csi-node-driver-registrar docker image /oss/kubernetes-csi/csi-node-driver-registrar
image.nodeDriverRegistrar.tag csi-node-driver-registrar docker image tag v2.5.1
image.nodeDriverRegistrar.pullPolicy csi-node-driver-registrar image pull policy IfNotPresent
imagePullSecrets Specify docker-registry secret names as an array [] (does not add image pull secrets to deployed pods)
serviceAccount.create whether create service account of csi-azuredisk-controller, csi-azuredisk-node, and snapshot-controller true
serviceAccount.controller name of service account for csi-azuredisk-controller csi-azuredisk-controller-sa
serviceAccount.node name of service account for csi-azuredisk-node csi-azuredisk-node-sa
serviceAccount.snapshotController name of service account for csi-snapshot-controller csi-snapshot-controller-sa
rbac.create whether create rbac of csi-azuredisk-controller true
rbac.name driver name in rbac role azuredisk
controller.name name of driver deployment csi-azuredisk-controller
controller.cloudConfigSecretName cloud config secret name of controller driver azure-cloud-provider
controller.cloudConfigSecretNamespace cloud config secret namespace of controller driver kube-system
controller.allowEmptyCloudConfig Whether allow running controller driver without cloud config false
controller.replicas the replicas of csi-azuredisk-controller 2
controller.metricsPort metrics port of csi-azuredisk-controller 29604
controller.livenessProbe.healthPort health check port for liveness probe 29602
controller.runOnMaster run csi-azuredisk-controller on master node(deprecated on k8s 1.25+) false
controller.runOnControlPlane run controller on control plane node false
controller.vmssCacheTTLInSeconds vmss cache TTL in seconds (600 by default) -1 (use default value)
controller.vmType type of agent node. available values: vmss, standard `` (use default value in cloud config)
controller.logLevel controller driver log level 5
controller.tolerations controller pod tolerations
controller.affinity controller pod affinity {}
controller.nodeSelector controller pod node selector {}
controller.hostNetwork hostNetwork setting on controller driver(could be disabled if controller does not depend on MSI setting) true
controller.resources.csiProvisioner.limits.memory csi-provisioner memory limits 500Mi
controller.resources.csiProvisioner.requests.cpu csi-provisioner cpu requests 10m
controller.resources.csiProvisioner.requests.memory csi-provisioner memory requests 20Mi
controller.resources.csiAttacher.limits.memory csi-attacher memory limits 500Mi
controller.resources.csiAttacher.requests.cpu csi-attacher cpu requests 10m
controller.resources.csiAttacher.requests.memory csi-attacher memory requests 20Mi
controller.resources.csiResizer.limits.memory csi-resizer memory limits 500Mi
controller.resources.csiResizer.requests.cpu csi-resizer cpu requests 10m
controller.resources.csiResizer.requests.memory csi-resizer memory requests 20Mi
controller.resources.csiSnapshotter.limits.memory csi-snapshotter memory limits 500Mi
controller.resources.csiSnapshotter.requests.cpu csi-snapshotter cpu requests 10m
controller.resources.csiSnapshotter.requests.memory csi-snapshotter memory requests 20Mi
controller.resources.livenessProbe.limits.memory liveness-probe memory limits 100Mi
controller.resources.livenessProbe.requests.cpu liveness-probe cpu requests 10m
controller.resources.livenessProbe.requests.memory liveness-probe memory requests 20Mi
controller.resources.azuredisk.limits.memory azuredisk memory limits 500Mi
controller.resources.azuredisk.requests.cpu azuredisk cpu requests 10m
controller.resources.azuredisk.requests.memory azuredisk memory requests 20Mi
node.cloudConfigSecretName cloud config secret name of node driver azure-cloud-provider
node.cloudConfigSecretNamespace cloud config secret namespace of node driver kube-system
node.supportZone Whether get zone info in NodeGetInfo on the node (requires instance metadata support) true
node.allowEmptyCloudConfig Whether allow running node driver without cloud config true
node.maxUnavailable maxUnavailable value of driver node daemonset 1
node.metricsPort metrics port of csi-azuredisk-node 29605
node.livenessProbe.healthPort health check port for liveness probe 29603
node.logLevel node driver log level 5
snapshot.enabled whether enable snapshot feature false
snapshot.image.csiSnapshotter.repository csi-snapshotter docker image /oss/kubernetes-csi/csi-snapshotter
snapshot.image.csiSnapshotter.tag csi-snapshotter docker image tag v5.0.1
snapshot.image.csiSnapshotter.pullPolicy csi-snapshotter image pull policy IfNotPresent
snapshot.image.csiSnapshotController.repository snapshot-controller docker image /oss/kubernetes-csi/snapshot-controller
snapshot.image.csiSnapshotController.tag snapshot-controller docker image tag v5.0.1
snapshot.image.csiSnapshotController.pullPolicy snapshot-controller image pull policy IfNotPresent
snapshot.snapshotController.name snapshot controller name csi-snapshot-controller
snapshot.snapshotController.replicas the replicas of snapshot-controller 2
snapshot.snapshotController.resources.limits.memory csi-snapshot-controller memory limits 100Mi
snapshot.snapshotController.resources.requests.cpu csi-snapshot-controller cpu requests 10m
snapshot.snapshotController.resources.requests.memory csi-snapshot-controller memory requests 20Mi
linux.enabled whether enable linux feature true
linux.dsName name of driver daemonset on linux csi-azuredisk-node
linux.kubelet configure kubelet directory path on Linux agent node /var/lib/kubelet
linux.getNodeInfoFromLabels get node info from node labels instead of IMDS on Linux agent node false
linux.distro configure ssl certificates for different Linux distribution(available values: debian, fedora) debian
linux.tolerations linux node driver tolerations
linux.affinity linux node pod affinity {}
linux.nodeSelector linux node pod node selector {}
linux.hostNetwork hostNetwork setting on linux node driver(could be disabled if perfProfile is none) true
linux.resources.livenessProbe.limits.memory liveness-probe memory limits 100Mi
linux.resources.livenessProbe.requests.cpu liveness-probe cpu requests 10m
linux.resources.livenessProbe.requests.memory liveness-probe memory requests 20Mi
linux.resources.nodeDriverRegistrar.limits.memory csi-node-driver-registrar memory limits 100Mi
linux.resources.nodeDriverRegistrar.requests.cpu csi-node-driver-registrar cpu requests 10m
linux.resources.nodeDriverRegistrar.requests.memory csi-node-driver-registrar memory requests 20Mi
linux.resources.azuredisk.limits.memory azuredisk memory limits 200Mi
linux.resources.azuredisk.requests.cpu azuredisk cpu requests 10m
linux.resources.azuredisk.requests.memory azuredisk memory requests 20Mi
windows.enabled whether enable windows feature true
windows.dsName name of driver daemonset on windows csi-azuredisk-node-win
windows.kubelet configure kubelet directory path on Windows agent node 'C:\var\lib\kubelet'
windows.getNodeInfoFromLabels get node info from node labels instead of IMDS on windows agent node false
windows.tolerations windows node driver tolerations
windows.affinity windows node pod affinity {}
windows.nodeSelector windows node pod node selector {}
windows.resources.livenessProbe.limits.memory liveness-probe memory limits 100Mi
windows.resources.livenessProbe.requests.cpu liveness-probe cpu requests 10m
windows.resources.livenessProbe.requests.memory liveness-probe memory requests 40Mi
windows.resources.nodeDriverRegistrar.limits.memory csi-node-driver-registrar memory limits 100Mi
windows.resources.nodeDriverRegistrar.requests.cpu csi-node-driver-registrar cpu requests 30m
windows.resources.nodeDriverRegistrar.requests.memory csi-node-driver-registrar memory requests 40Mi
windows.resources.azuredisk.limits.memory azuredisk memory limits 200Mi
windows.resources.azuredisk.requests.cpu azuredisk cpu requests 10m
windows.resources.azuredisk.requests.memory azuredisk memory requests 40Mi
windows.useHostProcessContainers use HostProcessContainers for deployment false
cloud cloud environment driver is running on AzurePublicCloud

Azure Disk CSI Driver V2 (Preview)

install Azure Disk CSI Driver V2 (Preview)

Applicable to any Kubernetes cluster without the Azure Disk CSI Driver V1 installed. If V1 is installed, proceed to side-by-side installation instructions below. The V1 driver is installed by default in AKS clusters with Kubernetes version 1.21 and later.

helm install azuredisk-csi-driver azuredisk-csi-driver/azuredisk-csi-driver --namespace kube-system --version v2.0.0-beta.6

install Azure Disk CSI Driver V2 side-by-side with Azure Disk CSI Driver V1 (Preview)

Since VolumeSnapshot CRDs and other components are created first when V1 driver is installed, use the side-by-side-values.yaml to customize the V2 driver to run side-by-side with the V1 driver. Note that if you uninstall the V1 driver, you would have to update your V2 driver to install the necessary snapshot components that would have then been deleted.

helm install azuredisk-csi-driver-v2 azuredisk-csi-driver/azuredisk-csi-driver --namespace kube-system \
  --version v2.0.0-beta.6 \
  --values https://raw.githubusercontent.com/kubernetes-sigs/azuredisk-csi-driver/master/charts/v2.0.0-beta.6/azuredisk-csi-driver/side-by-side-values.yaml

NOTE: When installing the V2 driver side-by-side with the V1 driver in an AKS cluster, you will need to grant the agentpool service principal or managed identity Contributor access to the resource groups used to store managed disks. By default, this is the resource group prefixed by MC_ corresponding to your AKS cluster.

install driver with Prometheus monitors

>/tmp/azuredisk-csi-driver-overrides.yaml cat <<EOF
controller:
  metrics:
    service:
      enabled: true
      monitor:
        enabled: true
schedulerExtender:
  metrics:
    service:
      enabled: true
      monitor:
        enabled: true
EOF
helm install azuredisk-csi-driver azuredisk-csi-driver/azuredisk-csi-driver --namespace kube-system --version v2.0.0-beta.6 --values /tmp/azuredisk-csi-driver-overrides.yaml

upgrade Azure Disk CSI Driver V1 to V2 (Preview)

This assumes you have already installed Azure Disk CSI Driver V1 to a non-AKS cluster, e.g. one created using aks-engine or Cluster API Provider for Azure (CAPZ).

helm upgrade azure-csi-driver azuredisk-csi-driver/azuredisk-csi-driver --namespace kube-system --version v2.0.0-beta.6

Preview chart configuration

New or Updated Parameters for V2

In addition to the parameters supported by the V1 driver, Azure Disk CSI driver V2 adds or modifies the following parameters:

Parameter Description Default
image.azuredisk.tag Azure Disk CSI Driver V2 docker image tag v2.0.0-beta.6
image.curl.repository curl docker image docker.io/curlimages/curl
image.curl.tag curl docker image tag latest
image.curl.pullPolicy curl docker image pull policy IfNotPresent
image.schedulerExtender.repository Azure Disk CSI Driver V2 Scheduler Extender docker image /oss/csi/azdiskschedulerextender-csi
image.schedulerExtender.tag Azure Disk CSI Driver V2 Scheduler Extender docker image tag v2.0.0-beta.6
image.schedulerExtender.pullPolicy Azure Disk CSI Driver V2 Scheduler Extender docker image pull policy IfNotPresent
image.kubeScheduler.repository kube-scheduler docker image /oss/kubernetes/kube-scheduler
image.kubeScheduler.tag kube-scheduler docker image tag - this version should be the same as the Kubernetes cluster version v1.21.2
image.kubeScheduler.pullPolicy kube-scheduler docker image pull policy IfNotPresent
serviceAccount.schedulerExtender name of service account for Azure Disk CSI Driver V2 Scheduler Extender csi-azuredisk-scheduler-extender-sa
controller.metrics.port Azure Disk CSI Driver V2 controller metrics server port. This value replaces controller.metricsPort 29604
controller.metrics.service.enabled whether a Service is created for the Azure Disk CSI Driver V2 controller metrics server false
controller.metrics.service.monitor.enabled whether a ServiceMonitor is created for the Azure Disk CSI Driver V2 controller metrics server Service. false
schedulerExtender.name Azure Disk CSI Driver V2 Scheduler Extender deployment name csi-azuredisk-scheduler-extender
schedulerExtender.replicas Azure Disk CSI Driver V2 Scheduler Extender replica count 2
schedulerExtender.metrics.port Azure Disk CSI Driver V2 Scheduler Extender metrics server port 29604
schedulerExtender.metrics.service.enabled whether a Service is created for the Azure Disk CSI Driver V2 Scheduler Extender metrics server false
schedulerExtender.metrics.service.monitor.enabled whether a ServiceMonitor is created for the Azure Disk CSI Driver V2 Scheduler Extender metrics server Service. false
schedulerExtender.servicePort Azure Disk CSI Driver V2 Scheduler Extender service port 8889
schedulerExtender.affinity Azure Disk CSI Driver V2 Scheduler Extender pod affinity
schedulerExtender.tolerations Azure Disk CSI Driver V2 Scheduler Extender pod tolerations Tolerates scheduling to control plane
snapshot.createCRDs whether the snapshot CRDs are created true
storageClasses.create whether to create the default StorageClass instances for Azure Disk CSI Driver V2 true
storageClasses.enableZRS whether to create the StorageClass instances for ZRS disks (not supported in all regions) false
storageClasses.enableUltraSSD whether to create the StorageClass instances for UltraSSD disks (not supported in all regions) false
storageClasses.storageClassNames.standardLRS The StorageClass name for Standard_LRS disks azuredisk-standard-hdd-lrs
storageClasses.storageClassNames.standardSSDLRS The StorageClass name for StandardSSD_LRS disks azuredisk-standard-sdd-lrs
storageClasses.storageClassNames.standardSSDZRS The StorageClass name for StandardSSD_ZRS disks azuredisk-standard-sdd-zrs
storageClasses.storageClassNames.premiumLRS The StorageClass name for Premium_LRS disks azuredisk-premium-sdd-lrs
storageClasses.storageClassNames.premiumZRS The StorageClass name for Premium_ZRS disks azuredisk-premium-sdd-zrs
storageClasses.storageClassNames.ultraSSDLRS The StorageClass name for UltraSSD_LRS disks azuredisk-ultra-sdd-lrs

Troubleshooting

  • Add --wait -v=5 --debug in helm install command to get detailed error
  • Use kubectl describe to get more info