Repository navigation
chore(release): prepare kates-operator 0.3.0 - #681
Merged
Merged
Conversation
Chart and appVersion 0.3.0, and the README's install, verify and pull commands on it. The chart description drops the run kinds 0.3.0 removes (#675), and the CronJob example pins kates-tester 1.41.0. 0.2.0 was published before publish-operator.yml attested the chart (#677), so kates deploy --kates-mode operator refuses it; 0.3.0 is pushed, signed and attested.
bmscomp
added a commit
that referenced
this pull request
Nov 16, 2026
Moves every pin to 1.41.1, the tag this release publishes: the kates chart's appVersion and image tags (0.20.2), kates/k8s/deployment.yaml, the kates-tester pins in strimzi-operator 0.5.5, kafka-cluster 1.1.5, connect-cluster 2.2.5, mirror-maker2 0.12.5 and kates-chaos 2.6.2, the Litmus experiment pins, server.json, the registry docs, the runbook and recipes, the version matrix in appendix D, and kates-platform 0.10.2. The release exists so the CLI pins kates-operator 0.3.0 (#681): the v1.41.0 CLI pins 0.2.0, published without an attestation, which kates deploy --kates-mode operator refuses. Nothing under kates/src, cli/ or tester/ moved since v1.41.0.
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.
Chart and appVersion 0.3.0 for the
operator-v0.3.0tag; README install/verify/pull commands on it; description drops the run kinds removed in #675; CronJob example pins kates-tester 1.41.0.Why now: kates-operator 0.2.0 was published before #677 added the chart attestation step, so
kates deploy --kates-mode operator(v1.41.0) refuses it: GitHub holds no attestation for its digest. 0.3.0 also ships the quorum work since 0.2.0 (#664, #665, #672–#674, #676, #678, #679) and the breaking removal of KatesTest/KafkaCompliance (#675).Next: tag
operator-v0.3.0, then Kates v1.41.1 so the CLI pins kates-operator 0.3.0.