Blockchain goes Kubernetes
summary
Explains what it actually takes to run public blockchain nodes on Kubernetes: use statefulsets for disks, prefer a readiness probe over liveness, and monitor with Prometheus + exporters; many chains lack /metrics so a custom exporter is common. Notes Solana needs huge machines (256+ GB RAM, tens of TBs of disk) and ~65k TPS vs Bitcoin ~7 TPS, node syncs can take weeks, and production auto‑scaling requires a custom controller that clones snapshots to avoid re‑syncing. GCP’s Blockchain Node Engine (GA Jun 13) currently supports Ethereum at ~$500/mo.
AI-written summary · about
chapters (18)
- 0:00Blockchain on Kubernetes intro
- 1:05Blockchain infrastructure basics
- 3:38Blockchain node types
- 7:09Server requirements for nodes
- 8:13Run node on VM steps
- 9:40Node syncing and transactions
- 11:48Blockchain APIs and data
- 13:14Cloud node services
- 13:58Kubernetes architecture
- 14:42Infrastructure challenges
- 15:24Health checks for nodes
- 17:09Node failures and recovery
- 18:34Monitoring performance
- 20:42Custom metrics exporters
- 21:46Auto scaling strategies
- 22:53Quick vs advanced setup
- 23:35Speaker Background and Community Resources
- 25:01Q&A
related talks
29mWhy Does Blockchain Need Kubernetes?
40mChallenges and Solutions of Using Kubernetes for Blockchain Applications
37mRunning Blockchain as a Service on Kubernetes
22mAnatomy of a production grade Kubernetes cluster
24mState of Blockchain
48mScale and Performance Testing of Kubernetes: Answers for Specific Applications
45mDatabases on Kubernetes: Why you should care
21mLessons from the Field: Running Kubernetes at the Wellsite