Update test-network-k8s readme with High Availability doc link (#540)

Signed-off-by: David Enyeart <enyeart@us.ibm.com>
This commit is contained in:
Dave Enyeart 2021-11-22 03:54:39 -05:00 committed by GitHub
parent 22c54b4690
commit f898a3768d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -1,32 +1,32 @@
# Kubernetes Test Network # Kubernetes Test Network
Starting in release 2.0, Hyperledger introduced the [test-network](https://hyperledger-fabric.readthedocs.io/en/latest/test_network.html) Starting in release 2.0, Hyperledger introduced the [test-network](https://hyperledger-fabric.readthedocs.io/en/latest/test_network.html)
to serve as both an accelerator and learning resource for running Fabric networks. In addition to to serve as both an accelerator and learning resource for running Fabric networks. In addition to
providing a study guide for operational patterns, the test-network provided a baseline environment for members of providing a study guide for operational patterns, the test-network provided a baseline environment for members of
the Fabric community to quickly get up to speed with a working, local system, author smart contracts, and develop the Fabric community to quickly get up to speed with a working, local system, author smart contracts, and develop
simple blockchain applications. simple blockchain applications.
While test-network provided a solid foundation for casual Fabric development, the over-reliance on While test-network provided a solid foundation for casual Fabric development, the over-reliance on
[Docker Compose](https://docs.docker.com/compose/) introduced tremendous, non-trivial complexity when transitioning [Docker Compose](https://docs.docker.com/compose/) introduced tremendous, non-trivial complexity when transitioning
applications to production. Without belaboring the many issues and anti-patterns present in the Compose-based applications to production. Without belaboring the many issues and anti-patterns present in the Compose-based
test network, we'll submit that the best path forward is to _align_ the development and production patterns around a test network, we'll submit that the best path forward is to _align_ the development and production patterns around a
common orchestration framework - Kubernetes. common orchestration framework - Kubernetes.
Similar to Fabric, Kubernetes introduces a steep learning curve and presents a dizzying array of operational Similar to Fabric, Kubernetes introduces a steep learning curve and presents a dizzying array of operational
flexibility. In this guide, we'll outline the design considerations in the [`./network`](../network) flexibility. In this guide, we'll outline the design considerations in the [`./network`](../network)
scripts, provide a supplement to the [Fabric CA Deployment Guide](https://hyperledger-fabric-ca.readthedocs.io/en/latest/deployguide/ca-deploy.html), scripts, provide a supplement to the [Fabric CA Deployment Guide](https://hyperledger-fabric-ca.readthedocs.io/en/latest/deployguide/ca-deploy.html),
and build up to a reference model for realistic production deployments on Kubernetes. and build up to a reference model for realistic production deployments on Kubernetes.
_Ahoy!_ _Ahoy!_
## Network Topology ## Network Topology
The Kube test network establishes as consortium among a dedicated ordering organization and two peer organizations. The Kube test network establishes as consortium among a dedicated ordering organization and two peer organizations.
Participation in the network is managed over a channel, and transactions are committed to the blockchain ledgers by Participation in the network is managed over a channel, and transactions are committed to the blockchain ledgers by
invoking the [asset-transfer-basic](https://github.com/hyperledgendary/fabric-ccaas-asset-transfer-basic) invoking the [asset-transfer-basic](https://github.com/hyperledgendary/fabric-ccaas-asset-transfer-basic)
_Chaincode-as-a-Service_ running in a shared Kubernetes namespace. Each organization maintains indepedendent TLS _Chaincode-as-a-Service_ running in a shared Kubernetes namespace. Each organization maintains indepedendent TLS
and ECert CAs for management of local, channel, and user MSP contexts. and ECert CAs for management of local, channel, and user MSP contexts.
![Test Network](images/test-network.png) ![Test Network](images/test-network.png)
@ -34,16 +34,16 @@ and ECert CAs for management of local, channel, and user MSP contexts.
## Detailed Guides ## Detailed Guides
- [`./network`](NETWORK.md) - [`./network`](NETWORK.md)
- [Working with Kubernetes](KUBERNETES.md) - [Working with Kubernetes](KUBERNETES.md)
- [Certificate Authorities](CA.md) - [Certificate Authorities](CA.md)
- [Planning for a CA](CA.md#planning-for-a-ca) - [Planning for a CA](CA.md#planning-for-a-ca)
- [Deploy the TLS CAs](CA.md#deploy-the-tls-cas) - [Deploy the TLS CAs](CA.md#deploy-the-tls-cas)
- [Deploy the ECert CAs](CA.md#deploy-the-organization-ca) - [Deploy the ECert CAs](CA.md#deploy-the-organization-ca)
- [Launching the Test Network](TEST_NETWORK.md) - [Launching the Test Network](TEST_NETWORK.md)
- [Registering and Enrolling Identities](CA.md#registering-and-enrolling-identities) - [Registering and Enrolling Identities](CA.md#registering-and-enrolling-identities)
- [Assembling Node MSPs](link) - [Assembling Node MSPs](link)
- [Deploy Orderers and Peers](link) - [Deploy Orderers and Peers](link)
- [Working with Channels](CHANNELS.md) - [Working with Channels](CHANNELS.md)
- [Working with Chaincode](CHAINCODE.md) - [Working with Chaincode](CHAINCODE.md)
- [Working with Applications](APPLICATIONS.md) - [Working with Applications](APPLICATIONS.md)
- [High Availability](HIGH_AVAILABILITY.md)