rancher/k3k

Prevent deleting wrong cluster when names are ambiguous

Open

#448 opened on Aug 29, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (77 forks)auto 404
buggood first issueteam/collie

Repository metrics

Stars
 (886 stars)
PR merge metrics
 (PR metrics pending)

Description

When two or more clusters share the same name but exist in different namespaces, running k3kcli cluster delete <cluster-name> without the --namespace flag can easily delete the wrong cluster.

The command currently defaults to the k3k-<cluster-name> namespace if one exists, which may not be the user's intention. This can lead to accidental data loss.

-> % k3kcli cluster list      
NAMESPACE   NAME                  MODE     STATUS    POLICY
default     foo                   shared   Unknown   <none>
k3k-foo     foo                   shared   Unknown   <none>

Expected Behavior

The CLI should detect the name collision and fail with an error message, requiring the user to specify the target with the --namespace flag to prevent accidental deletion.

Contributor guide

Research direction
Investigate the current cluster delete command logic to understand how it resolves names and check if there is a collision. Then implement a check that detects multiple clusters with the same name and returns an error prompting the user to use the namespace flag.
Tech stack
go
Domain
clidevops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60