hostpath-provisioner pods are not executed in tainted nodes

Summary

When I was trying to create a hostpath-provisioner PVC for my microk8s cluster I noticed that hostpath-provisioner could not create PVCs inside nodes tainted with NoSchedule effect. The problem is that when hostpath-provisioner creates a pod to create the storage path inside the node and the created pod doesn't contain a toleration to allow it to be executed in any node.

What Should Happen Instead?

hostpath-provisioned pods should be executed in any node even with NoScheduled and NoExecuted taints.

Reproduction Steps

Add a node inside your microk8s cluster.
Run microk8s kubectl taint test=true:NoScheduled to taint the node.
Enable hostpath-storage add-ons using microk8s enable hostpath-storage.
Add a pod and a PVC with tolerations:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: test-pvc
spec:
  accessModes: [ReadWriteOnce]
---
apiVersion: v1
kind: Pod
metadata:
  name: test-nginx
spec:
  volumes:
    - name: pvc
      persistentVolumeClaim:
        claimName: test-pvc
  tolerations:
    - key: "test"
      operator: "Equal"
      value: "true"
      effect: "NoSchedule"
  containers:
    - name: nginx
      image: nginx
      ports:
        - containerPort: 80
      volumeMounts:
        - name: pvc
          mountPath: /usr/share/nginx/html

Run microk8s kubectl -n kube-system get pods to find hostpath-provisioner-<node>-<hash> in Pending state.

Introspection Report

inspection-report.tar.gz

Can you suggest a fix?

hostpath-provisioner-<node>-<hash> could start wih the toleration so it could be scheduled in any node.

tolerations:
  - operator: Equals

Are you interested in contributing with a fix?

Yes.

canonical / microk8s