Add dualstack support to the framework behind flag

[purnesh42H]

Based on @larry-safran's proof of concept PR #88

[purnesh42H]

• Successfully Run ./run.sh bin/run_td_setup.py without --add_dualstack_support flag
• Successfully Run ./run.sh bin/run_td_setup.py --cmd=cleanup without --add_dualstack_support flag
• Successfully Run ./run.sh bin/run_td_setup.py with --add_dualstack_support flag
• Successfully Run ./run.sh bin/run_td_setup.py --cmd=cleanup with --add_dualstack_support flag

[purnesh42H]

Adhoc tests on grpc:1.65.x

• grpc/core/master/linux/grpc_xds_k8s_lb
• grpc/core/master/linux/grpc_xds_url_map
• grpc/core/master/linux/grpc_xds_v3
• grpc/core/master/linux/psm-csm

[sergiitk]

LGTM, but give it another local run against the dual-stack cluster to polish the issues like the one with incorrect deletion orders. Then merge the current master into this branch, and re-run the tests. I'll give it another look early tomorrow.

[sergiitk]

Oh, and please save the output of the local run - I'd like to give it a check in case we missed anything

[purnesh42H]

All test suites against 1.65.x after rebase with latest main

• grpc/core/master/linux/grpc_xds_k8s_lb
• grpc/core/master/linux/grpc_xds_url_map
• grpc/core/master/linux/grpc_xds_v3
• grpc/core/master/linux/psm-csm

[sergiitk]

• grpc/java/v1.65.x/branch/psm-security
• grpc/java/v1.65.x/branch/xds_k8s_lb
• grpc/java/v1.65.x/branch/xds_url_map
• grpc/java/v1.65.x/branch/psm-csm

[sergiitk]

@purnesh42H noticed that the jobs you ran weren't using this framework branch. Note the jobs I started above:

# [08:17:29 PDT] Parsed build request:
full_job_name: "grpc/java/v1.65.x/branch/psm-security"
scm_revision {
  github_scm_revision {
    commit_sha: "v1.65.x"
    name: "grpc-java"
    owner: "grpc"
    repository: "grpc-java"
  }
}
env_vars {
  key: "TEST_DRIVER_BRANCH"
  value: "add-dualstack-support"
}
env_vars {
  key: "TEST_DRIVER_REPO_OWNER"
  value: "purnesh42H"
}

Also - no need to run grpc/core/master/linux/grpc_xds_v3, this is legacy framework, which isn't affected by any changes to this repo.

[sergiitk]

Ah, my fault. For some reason I expected these env vars to show up in BUILD_CONFIG on this page: https://btx.cloud.google.com/invocations/88d2b23a-0c50-47f1-8b97-990496b008cd/details.

The jobs your started look right.

[sergiitk]

All looks good, except I suspect ClientDeploymentArgs won't work as we want to. Could you apply/accept suggestions I made, and I'll take a stab at getting the deployment args right.

[sergiitk]

Two items to address in the follow-up:

1. Move server runner's enable_dualstack to ServerDeploymentArgs
2. Fix the issue with deployment_args not merged in suites that override initKubernetesClientRunner, see https://github.com/grpc/psm-interop/pull/101/files#r1688415338