Thanks for the report! We purposely don't expose the fsname as config, but rather discover it in the charm:
https://github.com/charmed-kubernetes/ceph-csi-operator/blob/release_1.29/src/charm.py#L235-L244
The problem is that we also cache that value:
https://github.com/charmed-kubernetes/ceph-csi-operator/blob/release_1.29/src/charm.py#L283
So if ceph-csi comes in before ceph-fs is deployed/related, that value will be None (because ceph-fs hasn't created the fs yet). And then we're stuck with it as the fsname in the ceph-fs storage class.
Thanks for the report! We purposely don't expose the fsname as config, but rather discover it in the charm:
https:/ /github. com/charmed- kubernetes/ ceph-csi- operator/ blob/release_ 1.29/src/ charm.py# L235-L244
The problem is that we also cache that value:
https:/ /github. com/charmed- kubernetes/ ceph-csi- operator/ blob/release_ 1.29/src/ charm.py# L283
So if ceph-csi comes in before ceph-fs is deployed/related, that value will be None (because ceph-fs hasn't created the fs yet). And then we're stuck with it as the fsname in the ceph-fs storage class.