Running kubetest2-gke --down separately, does not delete clusters create by --up previously

[chrislovecnm]

Hi all

I am running kubetest2 gke --down --cluster-name bazel-test --project chris-love-operator-playground --zone us-central1-a --ignore-gcp-ssh-key and the gke cluster is not getting deleted.

kubetest2 gke --up --cluster-name bazel-test --project chris-love-operator-playground --zone us-central1-a --ignore-gcp-ssh-key created the cluster

[amwat]

Decoupled --up --down in general doesn't have good support yet, but we do want that eventually.

The intended way would be to run --down with the --run-id=<run id used during up> (this also doesn't work currently though).

/cc @chizhg

currently the projectClusterLayout is stored in-memory, we'll want to persist that under RunDir() for Down() to reuse.
Note: some of this is being planned to be tackled in #88 (comment)

[chizhg]

/cc @joshua-bone

[chrislovecnm]

@amwat is there a good way to exec a test command while running an --up --down? We need to run a bazel e2e test

[amwat]

Yup, you can use the exec tester.
kubetest2 gke --up --down --test=exec -- <mycommand or myscript.sh>

[chrislovecnm]

Yah I am trying

~/Workspace/bin/kubetest2 gke --down --cluster-name kubetest2 --project chris-love-operator-playground --zone us-central1-a --ignore-gcp-ssh-key --up --test=exec -- bazel test --stamp //e2e/... --test_arg=--pvc=true

[amwat]

/priority important-longterm

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[amwat]

/remove-lifecycle stale
/lifecycle frozen

Improvements in #88 will also help in this