<p>Kubernetes version: 1.13.4 (same problem on 1.13.2).</p>

<p>I self-host the cluster on digitalocean.</p>

<p>OS: coreos 2023.4.0</p>

<p>I have 2 volumes on one node:</p>

<pre><code>kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: local-storage
provisioner: kubernetes.io/no-provisioner
volumeBindingMode: WaitForFirstConsumer
---
kind: PersistentVolume
apiVersion: v1
metadata:
  name: prometheus-pv-volume
  labels:
    type: local
    name: prometheus-pv-volume
spec:
  storageClassName: local-storage
  capacity:
    storage: 100Gi
  accessModes:
    - ReadWriteOnce
  persistentVolumeReclaimPolicy: Retain
  volumeMode: Filesystem
  hostPath:
    path: "/prometheus-volume"
  nodeAffinity:
    required:
      nodeSelectorTerms:
      - matchExpressions:
        - key: node-role.kubernetes.io/monitoring
          operator: Exists
---
kind: PersistentVolume
apiVersion: v1
metadata:
  name: grafana-pv-volume
  labels:
    type: local
    name: grafana-pv-volume
spec:
  storageClassName: local-storage
  capacity:
    storage: 1Gi
  persistentVolumeReclaimPolicy: Retain
  volumeMode: Filesystem
  accessModes:
    - ReadWriteOnce
  hostPath:
    path: "/grafana-volume"
  nodeAffinity:
    required:
      nodeSelectorTerms:
      - matchExpressions:
        - key: node-role.kubernetes.io/monitoring
          operator: Exists
</code></pre>

<p>And 2 pvc's using them on a same node. Here is one:</p>

<pre><code>  storage:
volumeClaimTemplate:
  spec:
    storageClassName: local-storage
    selector:
      matchLabels:
        name: prometheus-pv-volume
    resources:
      requests:
        storage: 100Gi
</code></pre>

<p>Everything works fine.</p>

<p><code>kubectl get pv --all-namespaces</code> output:</p>

<pre><code>NAME                   CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                                           STORAGECLASS    REASON   AGE
grafana-pv-volume      1Gi        RWO            Retain           Bound    monitoring/grafana-storage                      local-storage            16m
prometheus-pv-volume   100Gi      RWO            Retain           Bound    monitoring/prometheus-k8s-db-prometheus-k8s-0   local-storage            16m
</code></pre>

<p><code>kubectl get pvc --all-namespaces</code> output:</p>

<pre><code>NAMESPACE    NAME                                 STATUS   VOLUME                 CAPACITY   ACCESS MODES   STORAGECLASS    AGE
monitoring   grafana-storage                      Bound    grafana-pv-volume      1Gi        RWO            local-storage   10m
monitoring   prometheus-k8s-db-prometheus-k8s-0   Bound    prometheus-pv-volume   100Gi      RWO            local-storage   10m
</code></pre>

<p>The problem is that im getting these log messages every 2 minutes from kube-controller-manager:</p>

<pre><code>W0302 17:16:07.877212       1 plugins.go:845] FindExpandablePluginBySpec(prometheus-pv-volume) -&gt; err:no volume plugin matched
W0302 17:16:07.877164       1 plugins.go:845] FindExpandablePluginBySpec(grafana-pv-volume) -&gt; err:no volume plugin matched
</code></pre>

<p>Why do they appear? How can i fix this?</p>

<p>Seems like this is safe to ignore message that was recently removed (Feb 20) and will not occur in future releases: <a href="https://github.com/kubernetes/kubernetes/pull/73901" rel="nofollow noreferrer">https://github.com/kubernetes/kubernetes/pull/73901</a></p>
