Re: Does Raft orderer work across multiple Kubernetes clusters?


Jay Guo
 

Nye,

It would be nice if you could share some technical details of k8s that harm p2p network. I believe it could benefit both communities (HL and CNCF)

cheers,
- J

On Tue, Nov 19, 2019 at 3:35 PM Nye Liu <nye@...> wrote:
Not to stray too far off topic, but k8s emerged from a client/server microservices/stack deployment requirement, not a p2p requirement.

Its popularity for that purpose has (unfortunately, IMO) bled into places it isn’t really appropriate for because there are more fullstack devs than p2p devs.

Just my 2 cents, I know it is an unpopular opinion.

On Nov 19, 2019, at 2:31 PM, Hakan Eryargi <hakan.eryargi@...> wrote:

I guess K8S is the preferred way to deploy many things not only Fabric ;) and we will go production in a few months with Fabric in K8S.

We are not mixing K8S clusters for now, as it's not a requirement ATM, but will eventually be the case, mixing K8S with other K8S or on premises or whatever. That time possibly my preferred way of doing it will be using hostAliases to point to other nodes.  

Check Raft orderer section in our repo for how we do it:
https://github.com/APGGroeiFabriek/PIVT#scaled-up-raft-network  

On Tue, Nov 19, 2019 at 11:23 PM Yueming Xu <yxucolo@...> wrote:
So, in the case of a network across 2 k8s clusters, I have to make all orderer nodes accessible outside of k8s, and put the public host names and ports in the genesis block.  Correct?  K8s is still a preferred way to deploy the fabric network as I can see it, so such scenario will occur in production.  Thanks.



Join fabric@lists.hyperledger.org to automatically receive all group messages.