Repository navigation
docs: explain the Kates operator mode, and that standalone is unchanged - #686
Merged
Merged
Conversation
A new book chapter, Running Kates Under the Kates Operator, after the Deployment Guide: the two modes side by side, what stays the same in the default standalone mode (the quorum is off unless the operator configures peers; the drain switch and the health quorum block are additions), the one change for early operator users (KatesTest and KafkaCompliance), deploying with --kates-mode operator, the Kates resource's conditions, the quorum and its failover, drained upgrades, a lost node, a lost majority, a Helm install, switching modes and the limits. Outputs are from panda. Tutorial 16 runs the quorum on panda: deploy, read the resource, use the same CLI, kill the leader, drain, lose a node, switch back. The Deployment Guide, Upgrade Playbook, Part V page, glossary, concept registry, book README, tutorials 1 and 8, the tutorials index and the README point to both.
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.
What
--kates-mode operator, theKatesresource's conditions, the quorum and failover, drained upgrades, a lost node, a lost majority, a Helm install, switching modes and the limits.panda. It deploys three members, reads the resource, uses the same CLI, kills the leader, drains, loses a node and switches back.gl-kates-operator), the concept registry, the book README, tutorials 1 and 8, the tutorials index and the README.Compatibility claims, and where they come from
--kates-modedefaults tostandalone(cli/cmd/deploy.go:142).kates.quorum.peersis set (kates/src/main/resources/application.properties:482), and only the operator sets it. A standalone/api/healthshows"quorum":{"enabled":false}(Quorum.health()).cli/cmd/deploy_kates_operator.go).KatesTestandKafkaCompliancewere removed (feat(operator)!: remove KatesTest and KafkaCompliance #675). The chapter says so and links the chart README's upgrade steps.Tests
check-book-style.sh,book_metrics.py(new page at zero),gen-book-index.py --check(index regenerated),gen-chart-table.sh --check, a relative-link and fragment check on every changed file, and a fullquarto render --to htmlin a scratch copy withcheck-book-fragments.py(all fragment links land).kubectl get kates, pods, Services and health outputs are captured frompandarunning v1.41.2 with three members.Worth a look
Going back from operator mode to standalone without
kates cleanlikely trips Helm.installKatesResourcecreateskates-api-keywithkubectl apply, without Helm ownership labels, sohelm install katesshould refuse to adopt it. The tutorial and chapter tell you to delete that Secret first. This is from reading the code, not from a run.