You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The JuiceFS CSI driver is ignoring the volumeHandle parameter in PersistentVolumes and mounting all pods to the same JuiceFS volume (influxdb), regardless of the different volume configurations specified in their respective secrets.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
The JuiceFS CSI driver is ignoring the
volumeHandleparameter in PersistentVolumes and mounting all pods to the same JuiceFS volume (influxdb), regardless of the different volume configurations specified in their respective secrets.Environment
http://s3-object-storage:8333/juicefs)[etcd://<etcd-node-1>:2379,<etcd-node-2>:2379,<etcd-node-3>:2379]/jfs)Expected Behavior
Each pod should mount its own JuiceFS volume as specified by:
volumeHandlein the PersistentVolumenamefield in the corresponding secretActual Behavior
All pods mount the same JuiceFS volume (
influxdb), even when they have:volumeHandlevaluesnamefieldsEvidence
Pod Mount Points
All three pods mount
JuiceFS:influxdbdespite having different configurations.PersistentVolume Configuration
volumeHandle values are unique and correct.
Secret Configuration
Each pod references a different secret with unique
namefields:Pod 1 Secret (namespace: influxdb)
Pod 2 Secret (namespace: influxdb-recp-time)
Pod 3 Secret (namespace: monitoring)
Do you believe there’s a mistake in my configuration? Could you help me identify and fix it? Thanks for the support
Beta Was this translation helpful? Give feedback.
All reactions