the same logic that creates pods for regular tests is used for dualstack pods. In reality they are practically the same pods (readiness/ports/namespaces etc..). The only difference is dualstack pods have dual stack IPs. This ensure that same `shared` input is fed to the both test functions (dualstack and not dualstack)      So i have to disagree on creating a `testPod` function for dualstack :-)