For Updates testing we are doing a validation with continuous pings of the workloads and we track how many were lost, allowing us to fail the job if the lost ping count goes over some threshold. We should implement such functionality in the Adoption test suite as well.

Based on latest info https://github.com/openstack-k8s-operators/ci-framework/pull/1295 may perhaps be usable for Adoption – it should not depend on having podified control plane, we just need a floating IP of the already created workload to ping.

So this epic is perhaps only about supporting the CI folks in being able to use PR 1295 ping test in Adoption jobs, and making any tweaks to the pingtest if necessary. Alternatively we can copy the pingtest into the Adoption test suite to make sure we can start/stop the pings as needed without coupling with CI framework – that is the option that we started leaning towards in latest discussions.