I got the following error:

Events:
  Type     Reason              Age                 From                     Message
  ----     ------              ----                ----                     -------
  Warning  FailedScheduling    2m10s               default-scheduler        0/10 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/10 nodes are available: 10 No preemption victims found for incoming pod..
  Warning  FailedScheduling    2m8s                default-scheduler        0/10 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/10 nodes are available: 10 No preemption victims found for incoming pod..
  Normal   Scheduled           2m5s                default-scheduler        Successfully assigned kube-prometheus/prometheus-kube-prometheus-prometheus-2 to kube-master-10
  Warning  FailedAttachVolume  58s (x8 over 2m5s)  attachdetach-controller  AttachVolume.Attach failed for volume "pvc-86bff7a5-a368-4260-a8d7-5b75ee69d5f0" : CSINode kube-master-10 does not contain driver <http://driver.longhorn.io|driver.longhorn.io>
  Warning  FailedMount         3s                  kubelet                  Unable to attach or mount volumes: unmounted volumes=[prometheus-kube-prometheus-prometheus-db], unattached volumes=[prometheus-kube-prometheus-prometheus-db web-config config config-out prometheus-kube-prometheus-prometheus-rulefiles-0 kube-api-access-2lcwz tls-assets]: timed out waiting for the condition

What's wrong?

kubectl get <http://storageclasses.storage.k8s.io|storageclasses.storage.k8s.io>
NAME                 PROVISIONER          RECLAIMPOLICY   VOLUMEBINDINGMODE   ALLOWVOLUMEEXPANSION   AGE
longhorn (default)   <http://driver.longhorn.io|driver.longhorn.io>   Delete          Immediate           true                   177m

Hello @strong-sunset-30, it looks like your workload pod scheduled to

kube-master-10

, but your Longhorn deployment does not include

kube-master-10

. There are a number of ways to check this. One might be to execute

kubectl get pods -n longhorn-system -o wide | grep kube-master-10

and see if anything Longhorn-related is deployed there. If

kube-master-10

is a master node, it is not surprising that Longhorn is not deployed there. Longhorn cannot tolerate the

<http://node-role.kubernetes.io/control-plane:NoSchedule|node-role.kubernetes.io/control-plane:NoSchedule>

taint that is typically applied to master nodes and generally is not run on them. If you need Longhorn to run on a node that has a taint, please see this document: https://longhorn.io/docs/1.4.2/advanced-resources/deploy/taint-toleration/.

Yes, i think the taint is the Problem. I don't think about that, i'll try it and check if it works