Org is waiting for CA when first creates network by Kubernetes
Linkadi98 opened this issue · 2 comments
I have tried the latest code in main branch to check k8s support. I use minikube on local to test with installed tools as fablo suggestion. When I use fablo recreate or fablo up command to start the network in minikube, the step Deploying Org1 CA stucks with this log
Generating network config
FABLO_VERSION: 1.2.1-unstable.0
FABLO_CONFIG: /root/hyperledger-fabric/nodejs/fablo-config.json
FABLO_NETWORK_ROOT: /root/hyperledger-fabric/nodejs/fablo-target
Used network config: /network/workspace/../../network/fablo-config.json
Fabric version is: 2.4.7
Validation errors count: 0
Validation warnings count: 0
create fabric-config/.gitignore
create fabric-k8s/.env
create fabric-k8s/scripts/base-functions.sh
create fabric-k8s.sh
create fabric-k8s/scripts/base-help.sh
create fabric-k8s/scripts/util.sh
create fabric-k8s/scripts/chaincode-functions.sh
create hooks/post-generate.sh
Done & done !!! Try the network out:
-> fablo up - to start network
-> fablo help - to view all commands
fablo:setup-network
Formatting generated files
Executing post-generate hook
Executing Fablo Kubernetes command: up
============ 🦄 Checking dependencies... 🦄 ==============
Verifying kubectl-hlf installation...
/root/.krew/bin/kubectl-hlf
Verifying default kubernetes cluster
============ 🦄 Starting Network... 🦄 ==============
==== 🦄 Deploying Org1 CA 🦄 ====
INFO[0000] Certificate authority org1-ca created on namespace default
waiting for CA
waiting for CA
waiting for CA
waiting for CA
waiting for CA
waiting for CA
waiting for CA
waiting for CA
waiting for CA
waiting for CA
waiting for CA
waiting for CA
waiting for CA
waiting for CA
waiting for CA
waiting for CA
waiting for CA
With first try it shows waiting for CA and it doesn't continue to the next step.
Thanks for posting the issue! Unfortunately the k8s support for Fablo does not work very well, and we have some work towards fixing it, see #425. There is still a lot of work to do, so I cannot promise any date it will be done.
Under the hood Fablo uses Bevel operator. If you really need Kubernetes, you can try to start a network with pure Bevel. Also note it does not work with minikube - the kind tool is recommended.
If you don't need Kubernetes, I suggest you to use Fablo with Docker.
I switch to bevel operator after some searching, but the suggestion of bevel operator is not clear much so I hope fablo will fully support k8s in near future. I really love automation tool like fablo 😄.