Issue with peer join channel on Minikube about hgf-k8s-workshop HOT 13 CLOSED

I am sorry to tell you that I failed again. I had cleared the namespaces orderers and peers, and removed all associated secrets and volumes and networks.
it still connected to peer1-hlf-peer:7051 unsuccessfully.

from hgf-k8s-workshop.

I'm glad to tell you that it works on a proper Kubernetes environment I had built. my Orderer and Peer and CouchDB Charts version are 1.2.5, 1.2.4 and 1.0.5.
Compared with two environments, it may not work on Minikube. And Not Changed any of the files/configurations.

from hgf-k8s-workshop.

The config yaml is yours you had shown in dev_example, and the values yaml does.

from hgf-k8s-workshop.

Hi @yinwhm12

Please make sure you have deleted and purged the Helm chart deployments first and also removed all associated secrets and volumes (if you are using a non-pproduction environment you can delete the namespaces cas, orderers and peers)

Thanks,
Sasha

from hgf-k8s-workshop.

If you have existing secrets from other CAs, it is likely you will have issues with deploying.

from hgf-k8s-workshop.

my k8s is based on minikube(v0.32.0).

from hgf-k8s-workshop.

Hmm... I have not tested it on Minikube (it should still work, I expect), but we have extensively tested it on Azure cloud. I'd advise you to try deploying on a proper Kubernetes environment and see if that works at all.

It's very difficult to diagnose your issue without further information. You are using the latest master build and have not changed any of the files/configuration?

from hgf-k8s-workshop.

Maybe you have a try on Minikube in a case I had done in an improper way just followed your README.md shown.

from hgf-k8s-workshop.

Hi @yinwhm12, that's great to hear. I have not tested in Minikube yet but will endeavour to try at least for the dev example as soon as I have some time to do so.

I'll add it as planned feature for Nephos, our open source library for deploying HLF networks: aidtechnology/nephos#43

from hgf-k8s-workshop.

I am testing with minikube version: v0.34.1

Newest version is using CoreDNS rather than KubeDNS. Both are giving me issues. So it looks like an issue with the DNS service discovery on Minikube, similar to:

https://stackoverflow.com/questions/43152190/how-does-one-install-the-kube-dns-addon-for-minikube

from hgf-k8s-workshop.

I have managed to find a workaround, which will involve a small update to the Helm charts. Hopefully we will have Minikube support soon.

from hgf-k8s-workshop.

https://jira.hyperledger.org/browse/FAB-14305

from hgf-k8s-workshop.

Minikube now supported on Nephos, as described in the README.md here https://github.com/aidtechnology/nephos

from hgf-k8s-workshop.