Skip to content

check for existing cluster and delete if it already exists#239

Merged
gflarity merged 1 commit into
ai-dynamo:mainfrom
gflarity:check_for_existing_cluster
Nov 4, 2025
Merged

check for existing cluster and delete if it already exists#239
gflarity merged 1 commit into
ai-dynamo:mainfrom
gflarity:check_for_existing_cluster

Conversation

@gflarity

@gflarity gflarity commented Nov 1, 2025

Copy link
Copy Markdown
Contributor

What type of PR is this?

Feature

What this PR does / why we need it:

Occasionally a catastrophic failure will leave the the shared cluster kicking around. This checks for that condition and cleans it up as per @shayasoolin's suggestion.

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a API change?


Additional documentation e.g., enhancement proposals, usage docs, etc.:

NONE

@renormalize

Copy link
Copy Markdown
Contributor

Thanks for the suggestion @shayasoolin! I'd faced the same issue in my testing too, which forced me to kill the k3d cluster docker container.

Signed-off-by: Geoff Flarity <gflarity@nvidia.com>
@gflarity gflarity force-pushed the check_for_existing_cluster branch from 2f687bd to a7645de Compare November 3, 2025 19:39
@gflarity gflarity merged commit 22a9b7e into ai-dynamo:main Nov 4, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants