Repository navigation
chore(release): prepare v1.41.2 and kates-operator 0.3.1 - #684
Merged
Merged
Conversation
Moves every pin to 1.41.2, the tag this release publishes: the kates chart's appVersion and image tags (0.20.3), kates/k8s/deployment.yaml, the kates-tester pins in strimzi-operator 0.5.6, kafka-cluster 1.1.6, connect-cluster 2.2.6, mirror-maker2 0.12.6 and kates-chaos 2.6.3, the Litmus experiment pins, server.json, the registry docs, the runbook and recipes, the version matrix in appendix D, and kates-platform 0.10.3. kates-operator 0.3.1 (chart and appVersion, and the README's install, verify and pull commands) carries #683's operator side: NoQuorum for a backend older than the quorum, and a roll that replaces a stale member running no quorum first. The CronJob example pins kates-tester 1.41.2. The release ships #683: on kind, a release's published charts run the published backend instead of a stale local kates:native-local, and deploy stops at once on NoQuorum. Nothing under kates/src or tester/ moved since v1.41.0.
bmscomp
added a commit
that referenced
this pull request
Nov 16, 2026
…e copied (#685) * fix(scripts): wait for KafkaUser Secrets to settle before they are copied Strimzi's User Operator reads a user's Secret from its informer cache. The reconcile its own status update triggers can run before the cache holds the Secret the first reconcile created: it issues a new password, sets it in Kafka and overwrites the Secret (create, 409, update). A copy taken at the first Ready, as e2e-stack.sh and integration.yml do, can hold the password that was just replaced, and every Kafka call then fails authentication. That failed CI · Operator twice on main at f566a19, the tree #684's PR run passed with: both runs copied within a second of Ready. After the Ready wait, deploy-kafka-generic.sh now waits until the user Secrets' resource versions hold for 10 s (60 s at most). * fix(cli): kates deploy copies KafkaUser Secrets only once they hold The kafka-users wait now ends with the same settle as deploy-kafka-generic.sh: the KafkaUser Secrets' resource versions must hold for 10 s (a minute at most). Kates, Connect, Kafka UI and MirrorMaker 2 copy their Secrets after it, so none copies a password the User Operator replaces a moment later.
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.
Why
Ships #683. With v1.41.1,
kates deployon kind ran a stale localkates:native-localbuilt before the quorum. The operator then reportedNoLeaderindefinitely, and deploy waited out 10 minutes. #683 fixes the CLI and the operator, so both need a release:NoQuorumfor a backend older than the quorum, and a roll that replaces a stale member running no quorum first.NoQuorum. ItsChartVersionspin kates-operator 0.3.1.What changes
kates/k8s/deployment.yaml, the kates-tester pins (strimzi-operator 0.5.6, kafka-cluster 1.1.6, connect-cluster 2.2.6, mirror-maker2 0.12.6, kates-chaos 2.6.3), the Litmus experiments,server.json, the registry docs, the runbook and recipes, appendix D, and kates-platform 0.10.3.operator/chartmoves to 0.3.1, along with the README's install, verify and pull commands. The CronJob example pins kates-tester 1.41.2.kates/srcortester/moved.Release order
operator-v0.3.1on the merge commit, then wait forpublish-operator.ymlto push the image and chart, signed and attested.v1.41.2on the same commit. The CLI pins kates-operator 0.3.1, which has to be published before deploy pulls it.Tests
scripts/check-versions.sh,python3 scripts/chart_bumps.py("every changed chart carries a new version"),scripts/gen-version-matrix.sh --check,scripts/check-book-style.sh,gen-book-index.py --check, and yamllint on the Litmus experiments and chart values.helm linton all 16 charts plusoperator/chart, with dependencies built in a scratch copy.docs/registry/kates.md, 3 inserver.json.