mirror of
https://github.com/hyperledger/fabric-samples.git
synced 2026-06-17 15:35:09 +00:00
Instead of using the Fabric and Fabric CA three digit version (2.4.3), utilize the two digit version (2.4). Each time a Fabric/FabricCA release is pushed to dockerhub the two digit version tag is updated. This approach simplifies maintenance so that scripts don't have to be updated for every third digit release. Signed-off-by: David Enyeart <enyeart@us.ibm.com> |
||
|---|---|---|
| .. | ||
| chaincode | ||
| config | ||
| docs | ||
| kube | ||
| scripts | ||
| .gitignore | ||
| network | ||
| README.md | ||
Kubernetes Test Network
This project re-establishes the Hyperledger test-network as a cloud native application.
Objectives:
- Provide a simple, one click activity for running the Fabric test network.
- Provide a reference guide for deploying production-style networks on Kubernetes.
- Provide a cloud ready platform for developing chaincode, Gateway, and blockchain apps.
- Provide a Kube supplement to the Fabric CA Operations and Deployment guides.
- Support a transition to Chaincode as a Service.
- Support a transition from the Internal, Docker daemon to External Chaincode builders.
- Run on any Kube.
Fabric, Ahoy!
Prerequisites
Quickstart
Create a local Kubernetes cluster:
./network kind
Launch the network, create a channel, and deploy the basic-asset-transfer smart contract:
./network up
./network channel create
./network chaincode deploy
Invoke and query chaincode:
./network chaincode invoke '{"Args":["CreateAsset","1","blue","35","tom","1000"]}'
./network chaincode query '{"Args":["ReadAsset","1"]}'
Access the blockchain with a REST API:
./network rest-easy
Tear down the test network:
./network down
Tear down the cluster:
./network unkind
Detailed Guides
./network- Working with Kubernetes
- Certificate Authorities
- Launching the Test Network
- Working with Channels
- Working with Chaincode
- Working with Applications
Areas for Improvement / TODOs
- Refine the recipe and guidelines for use with
k3s/nerdctl(rancherdesktop.io) as an alternative to Docker / KIND. - Test the recipe with OCP, AWS, gcp, Azure, etc. (These should ONLY differ w.r.t. pvc and ingress)
- Address any of the 20+ todo: notes in network.sh
- Implement mutual TLS across peers, orderers, and clients.
- Caliper?