Skip to content

fix(cli): clean uninstalls the kafka-ui release - #505

Merged
bmscomp merged 1 commit into
mainfrom
fix/clean-kafka-ui
Oct 26, 2026
Merged

bmscomp merged 1 commit into
mainfrom
fix/clean-kafka-ui

Conversation

@bmscomp

@bmscomp bmscomp commented Oct 26, 2026

Copy link
Copy Markdown
Owner

Why

After kates clean, kates deploy status still showed the Strimzi operator and Kafka UI as deployed.

kates deploy installs Kafka UI as the kafka-ui Helm release (in --ui-ns, default kafka), but clean's release list didn't include it. Clean refuses to delete a namespace that holds a release it doesn't own, so it kept kafka. The krafter Kafka and its KafkaUsers stayed with it, so clean kept the Strimzi operator, its namespace and its CRDs as still in use. Clean reported all this in its kept list, but it read as clean not working.

Change

kafka-ui joins clean's app releases: in --namespace for the single topology and in --kafka-ns for isolated.

Checked

  • go test ./cmd and golangci-lint --new-from-rev pass.
  • Against a kind cluster left in that state, clean's plan (without --yes) now lists the kafka and strimzi-operator namespaces and the Strimzi CRDs for deletion.

Deliberately not done

Clean has no --ui-ns flag, so a Kafka UI deployed with a custom --ui-ns in the isolated topology is still looked for in --kafka-ns.

kates deploy installs Kafka UI as the kafka-ui release, but clean did not
list it. Clean then saw a release it does not own in the kafka namespace,
kept the namespace, and with the Kafka cluster still in it kept the
Strimzi operator too.
@bmscomp
bmscomp merged commit 41fec56 into main Oct 26, 2026
56 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