<p>Currently, the Fabric system consists of components running in multiple containers, which will be a challenge to maintain all those containers, thus I want to use some powerful containers management platform such as Kubernetes, to deploy Fabric. </p>

<p>Could anybody help ?  </p>

<p>Properly configuring and deploying Hyperledger Fabric components to Kubernetes is not trivial. And also is only one part of the puzzle. Populating the Fabric network regarding <code>channels</code> and <code>chaincodes</code> is also as important as launching the Fabric network. In my opinion, this second part is highly overlooked.</p>

<p>This GitHub repository called <a href="https://github.com/APGGroeiFabriek/PIVT" rel="nofollow noreferrer">Hyperledger Fabric meets Kubernetes</a> contains a couple of Helm charts to:</p>

<ul>
<li>Configure and launch the whole HL Fabric network, either:

<ul>
<li>A simple one, one peer per organization and Solo orderer</li>
<li>Or scaled up one, multiple peers per organization and Kafka or Raft orderer</li>
</ul></li>
<li>Populate the network declaratively:

<ul>
<li>Create the channels, join peers to channels, update channels for Anchor peers</li>
<li>Install/Instantiate all chaincodes, or some of them, or upgrade them to newer version</li>
</ul></li>
<li>Add new peer organizations to an already running network declaratively</li>
<li>Backup and restore the state of whole network</li>
</ul>

<p>Tested against Fabric versions 1.4.1 to 1.4.4 and just works fine.</p>

<p><strong>PS:</strong> I'm the author of these Helm charts. As mentioned in our repo, we had implemented these Helm charts for our project's needs, and as the results looks very promising, decided to share the source code with the HL Fabric community. Hopefully it will fill a large gap!</p>

<p>I can confirm, we are using the very same Helm charts in all our environments and CI/CD pipelines since May 2019 without any issues, and will go to production in early 2020.</p>
