The OpenStackDataPlaneNodeSet examples at [1] propose the following service deployment order:

...
- configure-network
- install-os
- configure-os
- frr
- validate-network 
...

And this is not valid when login to a podman registry is needed. That podman login happens during the configure-os service deployment. If the previous order is applied, podman login fails because there is no connectivity to the registry.

The following order would fix the issue, so all documents including "frr" service deployment should be updated accordingly:

...
- install-os
- configure-os
- configure-network
- frr
- validate-network 
...

Similar change has been proposed for CI configurations at [2].

 [1] https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html-single/deploying_a_dynamic_routing_environment/index

[2] https://github.com/openstack-k8s-operators/architecture/pull/709