This patch adds initial support for BFT orderers in the test-network-k8s.
When `TEST_NETWORK_ORDERER_TYPE` is set to `bft`, the network launches
four orderers configured with SmartBFT.
Signed-off-by: Tatsuya Sato <tatsuya.sato.so@hitachi.com>
* seperate namespace for each organization
Signed-off-by: Basil K Y <techiebasil@gmail.com>
* rest server working
Signed-off-by: Basil K Y <techiebasil@gmail.com>
* use single namespace by default, fix k8s buider
Signed-off-by: Basil K Y <techiebasil@gmail.com>
* added ci test for testing k8s n/w on multiple namespaces
Signed-off-by: Basil K Y <techiebasil@gmail.com>
* fix: access rest server via gateway
Signed-off-by: Basil K Y <techiebasil@gmail.com>
Signed-off-by: Basil K Y <techiebasil@gmail.com>
* Run RCAADMIN registration on the host OS, not in k8s
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* Fix a typo that caused the log trailer to not exit cleanly on error
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* allow a node registration to have been previously created. This allows for multiple 'network up' targets to be run.
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* Support the fabric-builder-k8s for the chaincode "easy button."
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* Run the CI/CD test suite using the correct matrix env for k8s builder
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* Incorporate review feedback : remove zz_unused and pkgk8scc routines
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* Access the test network services via a local Nginx ingress controller.
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* Run E2E / CI test suite against the Ingress based k8s test network
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* Improved wait for Nginx Ingress - this was causing some test flakes
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* impl for couchdb supports in test0network8s as hardcode
Signed-off-by: Sam Yuan <yy19902439@126.com>
* fix up according to pr review comments
Signed-off-by: Sam Yuan <yy19902439@126.com>
- Add a new label to each peer to mark which org it is in
- Create new service per org, that matches this label - so the service can pick from one of multiple pods
- Update the kubeproxy to give more choice of ha stratergies
- Update the application configmaps and samples to refer to this new service rather than specific peers
Signed-off-by: Matthew B White <whitemat@uk.ibm.com>
* Run the fabric test network on Kubernetes
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* Re-LINT
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
