Aleksei Sviridkin 264ce47602 fix(kafka): delete the release's StrimziPodSets on uninstall ...

On a cluster upgraded from Strimzi 0.x, deleting a Kafka application
leaves its brokers running. kube-controller-manager's garbage collector
first saw the StrimziPodSets under v1beta2 and never updates that
record, so once v1beta2 is no longer served it retries them forever
instead of deleting them, until kube-controller-manager restarts
(kubernetes/kubernetes#102641).

The pre-delete hook now deletes the release's StrimziPodSets after its
node pools, so uninstall no longer depends on garbage collection for
the brokers. An absent CRD is not a failure; any other error fails the
hook like the pool delete does, because Helm never runs it for the
release again.

Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>

2026-10-17 01:24:12 +03:00

..

apps

fix(kafka): delete the release's StrimziPodSets on uninstall

2026-10-17 01:24:12 +03:00

core

build(kafka-operator): vendor Strimzi 1.2.0

2026-10-17 01:24:11 +03:00

extra

fix(etcd): leave compaction to etcd and pass the real quota to defrag

2026-10-11 20:21:26 +03:00

library

feat(kubernetes-nodes): let CDI trust a self-hosted Talos image factory

2026-10-10 22:36:49 +03:00

system

chore(kafka, kafka-operator): drop the JVM sizing workaround

2026-10-17 01:24:11 +03:00

tests/cozy-lib-tests

feat(kubernetes-nodes): let CDI trust a self-hosted Talos image factory

2026-10-10 22:36:49 +03:00