A worked example, written as an ordinary post, so that every prose element the theme styles appears at least once on one page. The story is invented; the markup is not.
It was past midnight and the automation pipeline had crashed. Again. It had been failing for days — same pattern, same timing, always when the network got serious. And the diagnosis had finally turned up.
The symptom
Every time the pipeline pulled a large image, the node went NotReady. Not slowly. Instantly.
kubectl get nodes
NAME STATUS ROLES AGE VERSION
homelab NotReady control-plane 212d v1.31.2The bottleneck is never where you expect it. It’s the cheapest part in the chain.
— a note to future me
Finding the bottleneck
I started with the obvious suspects: CPU, memory, disk. All fine. Then I looked at the network, and the numbers stopped making sense.
A third-level heading
Some inline elements: a link to the archive, some inline code,
bold text, and italics.
- A bullet in a list
- A second bullet, longer, so it wraps onto a second line and we can check the leading holds up
- A third
- Ordered one
- Ordered two
| Component | Rated | Actual |
|---|---|---|
| Switch | 1 Gbps | 1 Gbps |
| Extender LAN | 1 Gbps | 100 Mbps |
| NIC | 1 Gbps | 100 Mbps |
What I learned
Measure the boring parts first.
Footnotes
Goldmark renders footnotes, and the theme styles them: the reference is an accent superscript1, and the notes collect at the foot of the article behind a rule. Jumping to one marks it, so you can see which you landed on2.