Skip to content

fix(cli): the manual kind hint frees the control-plane zone - #613

Merged
bmscomp merged 1 commit into
mainfrom
fix/kind-hint-untaint
Nov 5, 2026
Merged

bmscomp merged 1 commit into
mainfrom
fix/kind-hint-untaint

Conversation

@bmscomp

@bmscomp bmscomp commented Nov 5, 2026

Copy link
Copy Markdown
Owner

Why

Without a terminal, kates deploy tells you to run kind create cluster --config config/cluster.yaml --name panda yourself. A cluster made that way keeps the control-plane taint, and alpha is one of the three zones the Kafka pools pin to. A deploy onto an existing cluster does not remove the taint, so the alpha pods wait Pending until the 15-minute timeout. Hit on a scratch cluster on 2026-11-05.

What

The hint gains the kubectl taint line that CreateKind and scripts/start-cluster.sh already run. TestResolveCluster_OfferKindNonTTYFailsWithoutPrompting pins it.

Deliberately not done

  • silent_wait.go still does not stop early on a taint plus an affinity. That is a change to a wait rule for a rare case; this closes the route that leads there.
  • The zones are not checked against the config's control-plane role: KindZones[0] is alpha in both copies of the kind config.

Tests

go test ./cmd ./pkg/cluster, go vet ./cmd, gofmt.

Without a terminal, kates deploy prints the kind create cluster command
to run by hand. A cluster made that way keeps the control-plane taint,
kates deploy does not remove it from an existing cluster, and the alpha
Kafka pods wait Pending for 15 minutes. The hint now gives the untaint
command that CreateKind runs itself.
@bmscomp
bmscomp merged commit 7a42bd5 into main Nov 5, 2026
64 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.

1 participant