Repository navigation
fix(website): show what the CLI really does, and restore the phone views - #605
Merged
Merged
Conversation
The hero command and scenario.yaml could not run: resilience run has no --type or --fault, and test lint found four unknown fields in the scenario. The scenario is now the file of a real run, its output is that run's, and a new step in the website workflow lints it so the page can't drift again. Its copy no longer says a scenario injects a fault, and maxErrorRate goes because test apply never checks it. No fault ran on the lab, so the hero terminal is labelled sample output and the two figures illustrative. Their commands, gate grade, POD_KILL and broker names are corrected. The quick start drops "five commands" and "in minutes", and adds the checkout, the current-context warning and make clean. On phones the diagram's boxes get their names back, and Kates moves to the comparison's first column.
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
A design critique scored the site 18/28. The worst finding: the page's two main examples were refused by the CLI.
kates resilience run --type LOAD --fault broker-pod-killfailed withunknown flag: --type, andkates test lintfound four errors in the page'sscenario.yaml. These are the critique's three P1s.What changed
real run, kates v1.37.0, Kind, 3 brokers, 2026-11-05.maxErrorRateis gone becausekates test applynever checks it, and the copy no longer says a scenario injects a fault.website.ymlnow lints the scenario from the page, so it can't drift again.sample output, and the section states that the two figures are illustrative.--min-grade(now C everywhere),POD_KILLand thekrafter-brokers-Nnames.git checkout, the current-context warning,make clean, and a note that the gate exits 1 below the grade.Checks
html-validate@9passes.go run . test lint, and it matches the file that ran.Deliberately not done
noop, and enabling it needs a cluster change that was not made. A real run can replace the sample numbers later.kates gate --min-grade Cfailed at grade D, so the sample figures are far tidier than a laptop result.The comparison table's column order changes on desktop too.