Since #2734, the Manila CSI node plugin requires the OpenStack metadata service (config drive or 169.254.169.254) to discover node identity. The --nodeid and --nodeaz flags were deprecated and are ignored.
#2734 aligned Manila with how Cinder CSI handles node identity. For Cinder this makes sense: the node must be a Nova VM for volume attach/detach to work, so the metadata service is always available. Manila doesn't have that constraint. Shares are mounted via NFS or CEPHFS on the host. The node doesn't need to be a Nova instance.
This breaks deployments where the CSI node plugin runs on hosts that aren't OpenStack VMs, such as bare metal k8s clusters or edge nodes. NodeGetInfo fails with an Internal error and the node plugin can't register.
Before #2734, operators could set --nodeid to the Kubernetes node name (via the downward API) and --nodeaz to a fixed value or leave it empty. That worked fine and should continue to work.
Metadata auto-detection is a good default, but it shouldn't be the only option. If --nodeid is explicitly set, the driver should use it instead of querying metadata.
Since #2734, the Manila CSI node plugin requires the OpenStack metadata service (config drive or 169.254.169.254) to discover node identity. The
--nodeidand--nodeazflags were deprecated and are ignored.#2734 aligned Manila with how Cinder CSI handles node identity. For Cinder this makes sense: the node must be a Nova VM for volume attach/detach to work, so the metadata service is always available. Manila doesn't have that constraint. Shares are mounted via NFS or CEPHFS on the host. The node doesn't need to be a Nova instance.
This breaks deployments where the CSI node plugin runs on hosts that aren't OpenStack VMs, such as bare metal k8s clusters or edge nodes.
NodeGetInfofails with an Internal error and the node plugin can't register.Before #2734, operators could set
--nodeidto the Kubernetes node name (via the downward API) and--nodeazto a fixed value or leave it empty. That worked fine and should continue to work.Metadata auto-detection is a good default, but it shouldn't be the only option. If
--nodeidis explicitly set, the driver should use it instead of querying metadata.