Issues:
1. When the name of NETWORK_NAME or NS in file "network" (i.e., the namespace in k8s) is changed from "test-network", the resources in the k8s cluster cannot be created successfully when the command "./network up" is executed.
Error message: error: the namespace from the provided object "test-network" does not match the namespace "xxxxxx". You must pass '--namespace=test-network' to perform this operation.
2. org2-cc.yaml is not completed.
Fix:
1. Replace "test-network" in yaml files in folder "kube" with "${NS}".
2. Complete "org2-cc-template.yaml" by referring to "org1-cc-template.yaml".
Signed-off-by: destinysky <kangrui10@126.com>
This patch fixes errors in the document.
Fix errors as follows:
- Change shell script arguments
- Correct display results
Signed-off-by: Satoshi Ito <satoshi.ito.tf@hitachi.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>
In chaincode debugging guidance, using the Docker host alias
`host.docker.internal` is assumed.
But, the alias is not yet supported for Linux.
So, this patch adds its alternate procedure for Linux.
Signed-off-by: Tatsuya Sato <tatsuya.sato.so@hitachi.com>
* Addresses Issue #548 by providing a simple guide for running Java chaincode as a service with a local debugger.
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* missed a couple of bash syntax errors
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* Add metadata and activate examples to the CC README
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* move ccpackage/ contents into network script
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* Fix CI test - Azure mounts git checkout at a different folder root path
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* Update test-network-k8s README with updated cc deploy commands
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* Run basic-asset transfer CI tests with Java + golang CC in Azure
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* remove (obsolete) test-net chaincode/ folder
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* Address some PR review feedback points - README reorg
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* Use the SDKs contract router Main, not a local entrypoint
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* bump the build - remove trailing newlines from a README
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
The Hyperledger provided Fabric peer images are only a sample so it would be good to make the k8s test network peer image configurable, for example to include a custom builder
Signed-off-by: James Taylor <jamest@uk.ibm.com>
This patch includes some minor improvements, such as:
- Fix typos and broken links
- Correct chaincode type of asset-transfer-basic-debug
(seems it should be ccaas)
Signed-off-by: Tatsuya Sato <tatsuya.sato.so@hitachi.com>
This patch supports for pulling all images to the local docker cache
and loading to KIND.
Also, this adds the missing docker image pulling (couchdb) for Fabric.
Signed-off-by: Tatsuya Sato <tatsuya.sato.so@hitachi.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>
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>
* 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>
* Changes to the test-network k8s deployment to use the
built-in as-a-service chaincode builder from the Peer Container
Signed-off-by: Matthew B White <whitemat@uk.ibm.com>
* Remove the ccaas init container from org2 peer; tweak docs on ccaas config
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
Co-authored-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* Address Issue #511 with docs and better error handling
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
* Set the TEST_NETWORK_FABRIC_VERSION in documentation for local development.
Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.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>
- updated the logging for the application command; wasn't very good
- added some information to the help option. the current settings
useful if you're not sure what you've set
Signed-off-by: Matthew B White <whitemat@uk.ibm.com>
