Challenges and Solutions of Using Kubernetes for Blockchain Applications
summary
Hyperledger Fabric runs as containers so Kubernetes fits but raises concrete problems and fixes: multi‑provider cluster setup and varying kubeconfig workflows; flaky PV behavior leads to creating a custom NFS StorageClass to get consistent mounts and writes; clustered components (Kafka/Zookeeper/orderers) need stable hostnames so Fabric uses StatefulSet + headless Service patterns; chaincode spawning real Docker containers forces a daemonset for Docker endpoints on every node; deployment ordering is handled by an installer (cello) that sequences and waits for services.
AI-written summary · about
chapters (14)
- 0:00Start
- 1:23Tong Li
- 2:34Agenda
- 3:51Blockchain Technology
- 7:29What is unique about blockchain
- 11:03Differences of Chains
- 18:40Why use KBS for fabric
- 26:59Challenges & Solutions - 2
- 28:30Challenges & Solutions - 3
- 28:46Challenges & Solutions 3
- 30:40Challenges & Solutions - 4
- 34:35Challenges & Solutions - 6
- 36:32Challenges & Solutions - 7
- 38:11Good news
related talks
39mMulti-tenancy & Blockchain: Deploying Hyperledger Fabric on Kubernetes
39mMulti-tenancy & Blockchain: Deploying Hyperledger Fabric on Kubernetes
29mWhy Does Blockchain Need Kubernetes?
34mHyperledger Fabric Operator: A Faster and Easier Way to Manage a Blockchain...
32mBuilding Blockchain as a Service via Hyperledger Cello
26mBlockchain goes Kubernetes
17mUsing Kubernetes+CF Stack as a Part of Blockchain CI/CD...
34mHyperledger Fabric Operator: A Faster and Easier Way to Manage a Blockchain...