Hi folks! Anyone using rook here?

Hey guys, not sure if this is the right place to ask, if it isn't please let me know what's the right channel. Basically I'm trying to figure out the exact mechanism being used to mount volumes on the node by the local path provisioner. Normally if you issue the mount command on the node you can get a clear view of the mounts coordinated by kubernetes (mostly overlay file systems that make all the magic happen), but for the local path provisioner volumes, even when traversing all existing namespaces and checking the volumes there I could not see any mounts being used (I was grepping for the dir path value used by microk8s in this case, which is

/opt/local-path-provisioner

)

Anyone notice any troubles using azure-file provisioners on the newer version? One of our old local clusters used to have azurefile persistent volumes and I'm having the hardest trouble doing that on a v1.24.9 cluster.

Warning  FailedAttachVolume  115s (x9 over 20m)  attachdetach-controller  AttachVolume.Attach failed for volume "azurefile-csi" : timed out waiting for external-attacher of <http://file.csi.azure.com|file.csi.azure.com> CSI driver to attach volume unique-volumeid3
  Warning  FailedMount         112s (x4 over 17m)  kubelet                  Unable to attach or mount volumes: unmounted volumes=[data], unattached volumes=[kube-api-access-pbntk data config]: timed out waiting for the condition

I've tried the azure-file, azurefile-csi drivers, I continue to get a plain "timed out waiting for the condition" error with no following logs on any of the containers. It's irritating because the configuration on 1.16 was straight forward and simple. I've tried different storageaccounts and everything. Any ideas?

@rich-potato-42868 has left the channel