This message was deleted.

For some reason (yet unknown), rebooting all the nodes of the cluster hosting Rancher did solve the issue. 🤔