test-network-k8s: Introduce initial support for BFT orderers

[satota2]

This PR adds initial support for BFT orderers in the test-network-k8s.
When TEST_NETWORK_ORDERER_TYPE is set to bft, the network launches four orderers configured with SmartBFT.

I plan to update the documentation after this PR is merged.

How to try

cd test-network-k8s

export TEST_NETWORK_FABRIC_VERSION=3.0
export TEST_NETWORK_ORDERER_TYPE=bft

./network kind
./network cluster init
./network up
./network channel create

./network chaincode deploy asset-transfer-basic ../asset-transfer-basic/chaincode-java
./network chaincode invoke asset-transfer-basic '{"Args":["InitLedger"]}'
./network chaincode query  asset-transfer-basic '{"Args":["ReadAsset","asset1"]}'

[bestbeforetoday]

For some reason, this does not work for me. I am running on Ubuntu 24.04.1 with Go 1.23.5 and Kind 0.26.0. I tested with Fabric binaries and Docker images at v3.0.0, the CA at v1.5.13 and TEST_NETWORK_FABRIC_VERSION environment variable set to 3.0.

With the TEST_NETWORK_ORDERER_TYPE environment variable unset, both the current main branch and this pull request branch ran successfully.

When using this pull request branch and the TEST_NETWORK_ORDERER_TYPE environment variable set to bft, I see the following error when running ./network channel create:

Fabric image versions: Peer (3.0.0), CA (1.5.13)
Fabric binary versions: Peer (3.0.0), CA (1.5.13)
Creating channel "mychannel":
✅ - Registering org Admin users ...
✅ - Enrolling org Admin users ...
✅ - Creating channel MSP ...
☠️ - Creating channel genesis block ...
main.main()
        /home/runner/work/fabric/fabric/cmd/configtxgen/main.go:237 +0x77d

Between each test I cleared down the environment using ./network down followed by ./network unkind.

[satota2]

@bestbeforetoday
Thank you for testing and providing detailed feedback. My apologies for the oversight—I missed adding the configtx template file for BFT in this PR. I’ve updated the PR to include the necessary configtx template file. Could you please review and test again with the updated changes?

[bestbeforetoday]

This works well for me now. I wonder if the automated build should also be updated to test both non-BFT and BFT cases to avoid any future regressions?

[satota2]

@bestbeforetoday
Thank you for confirming and merging. I agree that the automated build should be updated to test both non-BFT and BFT cases. I plan to work on this next.