[OisinKyne]

docs(obol-stack): v0.18.0 — Silver, the cluster memory cap and client memory limits

Summary

User docs for Obol Stack v0.18.0.

• installing-networks.mdx:
  • Silver in the consensus-client options, with a footnote: alpha, amd64 only, v0.18.0 or later, try a testnet first.
  • --execution-memory / --consensus-memory rows. They set the limit.
  • A Memory section: requests vs limits, how each client is told its limit, Hoodi beacon nodes getting mainnet's limits, the fit warning and what to do about it, and syncing every node after an upgrade.
• quickstart.mdx: a Memory section under "Step 2: Start the stack" on the cluster cap:
  • the default;
  • --node-memory / OBOL_NODE_MEMORY;
  • existing clusters;
  • docker update;
  • k3d only.

Test plan

• Docusaurus build (not run locally; CI). The new link ./quickstart.mdx#memory targets the new ### Memory heading.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud