Adding examples of CCAAS and support into the test-network-k8s

[mbwhite]

Using the variant of the peer's docker container from hyperledger/fabric#2990 this PR adapts the K8S deployment to use this inbuilt chaincode builder.

• creates two deployments of the chaincode for each peer
• uses the builders ability to template the fields in the connection.json

Signed-off-by: Matthew B White [email protected]

[jkneubuh]

I had success with this approach and the latest default builder PR. A couple of tweaks are still necessary:

• metadata.json should reference ccaas not external type

• org2/peer1 is still loading an init container with the fabric-ccaas-builder image from ghca.io, it should be scrubbed.

• org2/peer2 should also propagate the CHAINCODE_AS_A_SERVICE_BUILDER_CONFIG in env.

[jkneubuh]

This looks better but still needs the 'external' -> 'ccaas' type updated in the metadata.json files.

Also just a reminder (to @jkneubuh) that this PR should not land until after the gateway / 2.4.x images are available on the public repositories.

[mbwhite]

@jkneubuh I've updated this, and checked it's working with the very latest docker images from Artifactory.

Updated 15December - confirmed that this is still working as expected.

updates made

[mbwhite]

@jkneubuh the PR #560 gives the asset-transfer-basic/chaincode-typescript and asset-transfer-basic/chaincode-java dockerfiles... this PR should use those images rather than any others.

WIll need the other PR to land first though.

[jkneubuh]

Thanks Matthew I really like this PR. Working with the new, default CCAAS builder is a huge relief and really makes it easy to work with smart contracts on K8s.

I took the liberty of pushing a few extra changes into this branch / fork / PR. Feel free to squash the commits if desired:

• Bumped the ./network TEST_NETWORK_FABRIC_VERSION to 2.4.1. (Note: this PR still needs to linger for a couple more days until the patch images have been uploaded to the Docker Hub.)

• org 2's peer1 config yaml was still referencing the labs ccaas-builder image from ghcr.io in an init container. NONE of the peers reference the hyperledendary init container in the current PR.

• There were a couple of md docs referencing the hyperledgendary init container. Also scrubbed.

Overall, it looks great, works great, and ... just works. I really, really like how this opens the door for running chaincode endpoints in a local IDE/debugger, and is seamlessly linked up with the new builder. The use of the templating in the connection JSON is a brilliant technique to match the cc hash, independent of the service URL. Nice one.

Really great. I "triple-approve" : 👍 👍 👍

[mbwhite]

@jkneubuh thanks for the updates!!

must remember not to merge this just yet...