fix: Add orderly shutdown steps to all kuttl tests#963
Closed
Conversation
…ce deletion timeouts During namespace deletion, ZooKeeper and Kafka are terminated simultaneously. Kafka's controlled-shutdown retries ZK connections indefinitely, keeping the process alive for the full grace period and blocking namespace deletion past kuttl's 300s timeout. For ZK-mode tests: scale brokers to 0 via the CRD so the operator performs an orderly shutdown before ZK is removed. For KRaft-mode tests: scale brokers to 0, delete the KafkaCluster CR to stop reconciliation, then force-delete controller pods. Controllers cannot be scaled via the CRD due to a "no Kraft controllers found to build ConfigMap" error. All tests also set gracefulShutdownTimeout: 60s to bound the worst-case wait. Validated with a full nightly suite run (26/26 PASS). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Member
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
90-shutdown-kafka.yamlstep to all 11 kuttl test suites that gracefully scales down Kafka before kuttl deletes the namespacegracefulShutdownTimeout: 60sin install templates to bound the worst-case shutdown wait (default is 30 minutes)Problem
During namespace deletion, ZooKeeper/controllers and Kafka brokers are terminated simultaneously. In ZK-mode, Kafka's controlled-shutdown retries ZK connections indefinitely, keeping the process alive for the full
terminationGracePeriodSeconds(up to 30 minutes) and blocking namespace deletion well past kuttl's 300s timeout.Test plan
Related: #956
Definition of Done Checklist
Author
Reviewer
Acceptance
type/deprecationlabel & add to the deprecation scheduletype/experimentallabel & add to the experimental features tracker