Repository navigation
feat(operator)!: remove KatesTest and KafkaCompliance - #675
Merged
Merged
Conversation
O3b of plans/operator-kates-kind.md: 0.2.0 deprecated both run kinds, and 0.3.0 removes them. The operator now reconciles the Kates kind alone. Gone with them: both reconcilers and CRDs, their examples and e2e.sh; the kates-connection Secret and the connection.fallback mount; the Strimzi Kafka watch, kafka.namespaces, rbac.kafkaNamespaceRole and the kafka-reader Role; the kates_operator_tests and kates_operator_compliance_rules gauges; the client calls only they made (create, get, cancel, report, compliance, capabilities); the deprecation warning at start; the reconcile-at annotation, which only they read. BREAKING CHANGE: values setting kafka, connection or rbac.kafkaNamespaceRole are refused by the chart's schema. Delete every KatesTest and KafkaCompliance while 0.2.x runs, since 0.3.0 no longer clears a live KatesTest's finalizer, then upgrade, then delete the two CRDs. The chart README's "Upgrading to 0.3.0" gives the order.
bmscomp
added a commit
that referenced
this pull request
Nov 16, 2026
…on an empty disk (#679) * test(operator): print the quorum members' logs when the PostgreSQL handover check fails The resource is deleted before the workflow's Show the stack step, so a failed handover left nothing to read. main fails this check on every run since #675 merged on top of #674. * fix(quorum): a failed hand-over is retried at the next check, with another member A leader cut off from PostgreSQL handed over to the next member in kates.quorum.peers, and a failed transfer counted as a hand-over: the next try waited 2 minutes. In the e2e that member was the one fenced a step before; its outbound connections had not recovered, its election got no votes, and the old leader won the next one. Main has failed the check on every Operator run since. A transfer that fails, or after which this member still leads, no longer starts the 2-minute rest, and the next check, 5 s on, asks the member after the one that failed. e2e-node-loss.sh: on two nodes, a follower sharing one gets a new volume, which the scheduler places on the third, instead of failing. The anti-affinity is preferred, and a local volume pins a member. * ci(operator): untaint Kind's control plane for the node-loss test Kind keeps the control plane's NoSchedule taint when the cluster has workers, so the three members ran on two nodes and the node-loss test had no third to spread them over. * test(operator): print the leader's and the replaced member's logs when it has not caught up * test(operator): the node-loss test takes a worker without the test database The test PostgreSQL could share the lost node: every member then lost it, and the leader handed over by design while the test checked that it led throughout. The database now prefers the control plane, which the test never takes, and the lost node is never the database's. * fix(quorum): a member rebuilt on an empty disk has the leader step down Ratis 3.3.1's leader keeps the index a member matched before it lost its disk: it answers the member's INCONSISTENCY nextIndex=0 with heartbeats from that index, and the member stays at applied index -1 until the leader changes. A follower whose log is still empty 15 s after it knows a leader now asks that leader to step down, at most once a minute; the next leader starts replication over and sends the whole log. The node-loss e2e checks the leader only while the member is gone, and gives the catch-up 90 s. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
bmscomp
added a commit
that referenced
this pull request
Nov 16, 2026
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.
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.
O3b of
plans/operator-kates-kind.md. 0.2.0 deprecated both run kinds (D5: deprecate first, remove in 0.3.0), and this removes them. The operator now reconciles theKateskind alone. 34 files: 232 lines added, 4,139 deleted.What goes
wire.rs), the examples, andoperator/e2e.shwith its CI step.kates-connectionSecret lookup andconnection.fallback.connection.rsis now just the per-URL client cache theKateskind uses.Kafkawatch,kafka.namespaces,rbac.kafkaNamespaceRoleandtemplates/kafka-reader.yaml.kates_operator_testsandkates_operator_compliance_rulesgauges.kates.io/reconcile-atannotation, which only they read.resourceNameslose both kinds. The Secret rule narrows tokates-api-key.KatesCRD and refuses an unknown key (replica). The test-request schema leaves the Rust path filter.Breaking change
kafka,connectionandrbac.kafkaNamespaceRole, sohelm upgrade --reuse-valuesfrom 0.2.x fails, naming the key.KatesTest's finalizer), upgrade, then delete the two CRDs. Helm leaves CRDs in place.katesCLI) stays, and now reads its key from a Secret of your own.Proof
cargo fmt,clippy -D warnings,cargo test(workspace);crdgenregenerated, sochart/crdsholdskates.kates.io.yamlalone;helm lint; both RBAC scopes andwatchAnyNamespacerender; kubeconform v0.6.7 accepts a validKatesand refusesreplica.--reuse-valueswas refused withadditional properties 'kafka', 'connection' not allowed.Katesstayed Ready with its leader.operator/e2e-kates.shon that lab: 36/36.cargo deny, which isn't installed here. No dependency was added.