Hi, regarding the immutable must have randomly generated names issue: The issue is "solved" in the latest release v1.1.0 BUT if a new compute- node with same name got created, the change will interrupt connectivity to MQ of the nova-compute POD.[1] As the nova-operator recreates the nova-compute-node, a new MQ user with the same username (but different resource name) get's created and than we have 2 MQ users one old "failing" one new. With rolling out [2] the old one can get deleted, but as the username at MQ is the same, the new one don't work for the nova-compute node anymore, till infra-operator recreates the user. So [2]will lead to an interruption of nova-compute MQ connectivity. One "solution" would be to delete the finalizer for all MQ users stuck in immutable-State before rolling out the release. Or you hope, no actions are done to our OpenStack, till the MQ user got updated. Feel free to discuss possible solutions at [1] Regards Stefan [1] https://gitlab.com/yaook/operator/-/issues/630 [2] https://gitlab.com/yaook/operator/-/merge_requests/3331 -- Stefan Hoffmann DevOps-Engineer   Cloud&Heat Cloud&Heat Technologies GmbH Königsbrücker Straße 96 (Halle 15) | 01099 Dresden +49 351 479 367 36 stefan.hoffmann@cloudandheat.com | www.cloudandheat.com Green, Open, Efficient. Ihr Cloud-Service- und Cloud-Technologie-Provider aus Dresden. [1] Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann [1] Ihr Cloud-Service- und Cloud-Technologie-Provider aus Dresden. https://www.cloudandheat.com/