As the global service is still modeled on the NodeSet but acts on all the NodeSets connected to the Deployment handling of scale-in an scale-out with extra NodeSets needs special care that if missed can lead to a partially functioning deployment:

• when a new NodeSet is added to the Deployment only one of the NodeSets can list the global service and every NodeSet needs to be referred in the Deployment that does the scale out to ensure that the global service runs on both old and new nodes
• when a NodeSet is removed during a scale in the global service needs to be moved from the scaled in NodeSet to exactly one of the remaining NodeSets.

See the documentation added in for details https://github.com/openstack-k8s-operators/dataplane-operator/pull/869