The cinder-csi daemonset doesn't restart automatically if the openstack credentials are modified

Summary

The cinder-csi daemonset doesn't restart automatically if the openstack credentials are modified in the cinder-csi-cloud-config secret.

related references

Details

In case of rotation of the openstack credentials, the modification of the values and the apply.sh updates correctly the credentials in all the K8S secrets they need to be in, and the reconciliation succeeds apparently. However, the cinder-csi-nodeplugin is no longer capable of using the openstack APIs because it is still using the old credentials.

A manual restart of the openstack-cinder-csi-nodeplugin daemonset fixes the problem.

The restart should be automated.