3 commits

Author	SHA1	Message	Date
destinysky	9f844e5de3	Fix namespace in k8s configuration files (#784) ... 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>	2022-07-04 08:36:36 -04:00
jkneubuh	a3ae179efb	test-network-k8s : Connect to Fabric services via Nginx Ingress - READY FOR MERGE (#692) ... * 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>	2022-03-31 17:12:51 +01:00
jkneubuh	35be8f7425	Employs the Kubernetes cert-manager for storage and organization of TLS certificates. (#612) ... Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>	2022-02-08 09:31:09 +00:00

Renamed from test-network-k8s/kube/org2/org2-ecert-ca.yaml (Browse further)