We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What happened: mount pod resource no change
What you expected to happen: user global config resource
How to reproduce it (as minimally and precisely as possible):
mountPodPatch: - resources: limits: cpu: "2" memory: 4Gi requests: cpu: 100m memory: 256Mi - pvcSelector: matchLabels: custom-resources: "true" resources: requests: cpu: 100m memory: 512Mi
apiVersion: v1 kind: PersistentVolumeClaim metadata: name: fs-538424121676009018 namespace: ns-2263 lables: custom-resources: "true"
Anything else we need to know?
Environment:
kubectl version
The text was updated successfully, but these errors were encountered:
What is the volumeHandle of PV ?
Sorry, something went wrong.
pv:
apiVersion: v1 kind: PersistentVolume metadata: name: fs-538424121676009018-2263-pv spec: accessModes: - ReadWriteMany capacity: storage: 100Gi csi: driver: csi.juicefs.com fsType: juicefs nodePublishSecretRef: name: juicefs-secret namespace: juicefs volumeAttributes: juicefs/clean-cache: "true" volumeHandle: fs-538424121676009018-2263-pv mountOptions: - subdir=/fs-538424121676009018 - cache-dir=/data/juicefs_cache - cache-size=10240 persistentVolumeReclaimPolicy: Retain volumeMode: Filesystem
pvc
apiVersion: v1 kind: PersistentVolumeClaim metadata: name: fs-538424121676009018 namespace: ns-2263 labels: custom-resources: "true" spec: accessModes: - ReadWriteMany resources: requests: storage: 100Gi storageClassName: "" volumeMode: Filesystem volumeName: fs-538424121676009018-2263-pv
Please provide the log of juicefs CSI Node
No branches or pull requests
What happened:
mount pod resource no change
What you expected to happen:
user global config resource
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?
Environment:
kubectl version
):1.20.1The text was updated successfully, but these errors were encountered: