* 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>
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>
* 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>
