mirror of
https://github.com/hyperledger/fabric-samples.git
synced 2026-06-17 15:35:09 +00:00
d1b3253cc5
* 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>
81 lines
No EOL
2.9 KiB
Bash
Executable file
81 lines
No EOL
2.9 KiB
Bash
Executable file
#!/bin/bash
|
|
#
|
|
# Copyright IBM Corp All Rights Reserved
|
|
#
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
#
|
|
|
|
function launch_ECert_CAs() {
|
|
push_fn "Launching Fabric CAs"
|
|
|
|
apply_template kube/org0/org0-ca.yaml $ORG0_NS
|
|
apply_template kube/org1/org1-ca.yaml $ORG1_NS
|
|
apply_template kube/org2/org2-ca.yaml $ORG2_NS
|
|
|
|
kubectl -n $ORG0_NS rollout status deploy/org0-ca
|
|
kubectl -n $ORG1_NS rollout status deploy/org1-ca
|
|
kubectl -n $ORG2_NS rollout status deploy/org2-ca
|
|
|
|
# todo: this papers over a nasty bug whereby the CAs are ready, but sporadically refuse connections after a down / up
|
|
sleep 5
|
|
|
|
pop_fn
|
|
}
|
|
|
|
# experimental: create TLS CA issuers using cert-manager for each org.
|
|
function init_tls_cert_issuers() {
|
|
push_fn "Initializing TLS certificate Issuers"
|
|
|
|
# Create a self-signing certificate issuer / root TLS certificate for the blockchain.
|
|
# TODO : Bring-Your-Own-Key - allow the network bootstrap to read an optional ECDSA key pair for the TLS trust root CA.
|
|
kubectl -n $ORG0_NS apply -f kube/root-tls-cert-issuer.yaml
|
|
kubectl -n $ORG0_NS wait --timeout=30s --for=condition=Ready issuer/root-tls-cert-issuer
|
|
kubectl -n $ORG1_NS apply -f kube/root-tls-cert-issuer.yaml
|
|
kubectl -n $ORG1_NS wait --timeout=30s --for=condition=Ready issuer/root-tls-cert-issuer
|
|
kubectl -n $ORG2_NS apply -f kube/root-tls-cert-issuer.yaml
|
|
kubectl -n $ORG2_NS wait --timeout=30s --for=condition=Ready issuer/root-tls-cert-issuer
|
|
|
|
# Use the self-signing issuer to generate three Issuers, one for each org.
|
|
kubectl -n $ORG0_NS apply -f kube/org0/org0-tls-cert-issuer.yaml
|
|
kubectl -n $ORG1_NS apply -f kube/org1/org1-tls-cert-issuer.yaml
|
|
kubectl -n $ORG2_NS apply -f kube/org2/org2-tls-cert-issuer.yaml
|
|
|
|
kubectl -n $ORG0_NS wait --timeout=30s --for=condition=Ready issuer/org0-tls-cert-issuer
|
|
kubectl -n $ORG1_NS wait --timeout=30s --for=condition=Ready issuer/org1-tls-cert-issuer
|
|
kubectl -n $ORG2_NS wait --timeout=30s --for=condition=Ready issuer/org2-tls-cert-issuer
|
|
|
|
pop_fn
|
|
}
|
|
|
|
function enroll_bootstrap_ECert_CA_user() {
|
|
local org=$1
|
|
local ns=$2
|
|
|
|
# Determine the CA information and TLS certificate
|
|
CA_NAME=${org}-ca
|
|
CA_DIR=${TEMP_DIR}/cas/${CA_NAME}
|
|
mkdir -p ${CA_DIR}
|
|
|
|
# Read the CA's TLS certificate from the cert-manager CA secret
|
|
echo "retrieving ${CA_NAME} TLS root cert"
|
|
kubectl -n $ns get secret ${CA_NAME}-tls-cert -o json \
|
|
| jq -r .data.\"ca.crt\" \
|
|
| base64 -d \
|
|
> ${CA_DIR}/tlsca-cert.pem
|
|
|
|
# Enroll the root CA user
|
|
fabric-ca-client enroll \
|
|
--url https://${RCAADMIN_USER}:${RCAADMIN_PASS}@${CA_NAME}.${DOMAIN}:${NGINX_HTTPS_PORT} \
|
|
--tls.certfiles $TEMP_DIR/cas/${CA_NAME}/tlsca-cert.pem \
|
|
--mspdir $TEMP_DIR/enrollments/${org}/users/${RCAADMIN_USER}/msp
|
|
}
|
|
|
|
function enroll_bootstrap_ECert_CA_users() {
|
|
push_fn "Enrolling bootstrap ECert CA users"
|
|
|
|
enroll_bootstrap_ECert_CA_user org0 $ORG0_NS
|
|
enroll_bootstrap_ECert_CA_user org1 $ORG1_NS
|
|
enroll_bootstrap_ECert_CA_user org2 $ORG2_NS
|
|
|
|
pop_fn
|
|
} |