Open l-maciej opened 2 months ago
What happened:
When creating a PVC with size 200m created PV have capacity.storage set to 1 It happens only with this particular value (100Mi or 5Gi don't create such result)
What you expected to happen:
Create PV with capacity.storage: 200m
How to reproduce it: Create a PV using manifest
apiVersion: v1 kind: PersistentVolumeClaim metadata: name: kanboard-pvc-plugins spec: accessModes: - ReadWriteOnce storageClassName: nfs-hdd resources: requests: storage: 200m
Created PV will have spec
Name: pvc-1d8e37b6-cf6c-4ced-aaf3-94ffd9740cad Labels: <none> Annotations: pv.kubernetes.io/provisioned-by: nfs.csi.k8s.io volume.kubernetes.io/provisioner-deletion-secret-name: volume.kubernetes.io/provisioner-deletion-secret-namespace: Finalizers: [kubernetes.io/pv-protection] StorageClass: nfs-hdd Status: Bound Claim: workloads/kanboard-pvc-plugins Reclaim Policy: Retain Access Modes: RWO VolumeMode: Filesystem Capacity: 1 Node Affinity: <none> Message: Source: Type: CSI (a Container Storage Interface (CSI) volume source) Driver: nfs.csi.k8s.io FSType: VolumeHandle: pdev-nas-01#k3s-storage-hdd#pvc-1d8e37b6-cf6c-4ced-aaf3-94ffd9740cad## ReadOnly: false VolumeAttributes: csi.storage.k8s.io/pv/name=pvc-1d8e37b6-cf6c-4ced-aaf3-94ffd9740cad csi.storage.k8s.io/pvc/name=kanboard-pvc-plugins csi.storage.k8s.io/pvc/namespace=XXXX server=XXXX share=XXXX storage.kubernetes.io/csiProvisionerIdentity=1723720414355-5689-nfs.csi.k8s.io subdir=pvc-1d8e37b6-cf6c-4ced-aaf3-94ffd9740cad Events: <none>
Environment:
kubectl version
uname -a
I think the minimum size of pvc should be 1Gi
What happened:
When creating a PVC with size 200m created PV have capacity.storage set to 1 It happens only with this particular value (100Mi or 5Gi don't create such result)
What you expected to happen:
Create PV with capacity.storage: 200m
How to reproduce it: Create a PV using manifest
Created PV will have spec
Environment:
kubectl version
): 1.30.3uname -a
): 4.18.0-372.13.1.el8_6.x86_64