Closed vehagn closed 3 months ago
I think I managed to fix it myself. The StoreageClass
was wrong
I changed it to
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: proxmox-data
allowVolumeExpansion: true
parameters:
# I misunderstood this to be the backing volume filesystem, not the wanted filesystem.
csi.storage.k8s.io/fstype: xfs
# Changed this match an existing store ID. I misunderstood this to be the type of storage used,
# not the ID of a storage device
storage: local-zfs
cache: writethrough
ssd: "true"
mountOptions:
- noatime
provisioner: csi.proxmox.sinextra.dev
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
Closing this as I was able to resolve the issue by reading the documentation more thoroughly as explained in my previous comment.
Thank you for creating this CSI plugin, it was just what I was looking for!
Bug Report
Unable to get capacity of volumes
I'm unsure of how to debug this issue and would greatly appreciate any pointers on how to resolve it.
Description
I'm running Proxmox 8.2.2 and Kubernetes on a Debian 12 VM.
I had trouble getting Proxmox CCM to work, so I labelled my node manually:
and installed Proxmox CSI plugin from
https://raw.githubusercontent.com/sergelogvinov/proxmox-csi-plugin/v0.6.1/docs/deploy/proxmox-csi-plugin-release.yml
with the following config
I figured I had to cluster my one Proxmox node for this to work so I did (Is this necessary?)
I created the following
StorageClass
but I'm unsure if the name should be the same as the Proxmox volume.
Trying to run a variant of your example pod
it's unable to be scheduled due to not enough free storage.
Logs
Controller:
Node:
Environment
Plugin version:
Kubernetes version:
CSI capacity:
CSI resource on the node:
Node describe:
OS version