Practical overview
When it fits
Use it when you need Kubernetes-based automation for Hyperledger Fabric network components and are prepared to manage the cluster and supporting tools.
Who it is for
- Platform engineers managing Hyperledger Fabric on Kubernetes
- Fabric operators automating certificate, peer and ordering-service lifecycle tasks
- Teams deploying external chaincode in a Kubernetes environment
Documented uses
- Provision Fabric certificate authorities, peers and ordering services as Kubernetes resources.
- Manage ordering-service genesis material without manually provisioning cryptographic material.
- Renew certificates for Fabric deployments.
- Run Fabric chaincode as an external service in Kubernetes.
Requirements & limits
The project is published under the Apache-2.0 license. The documented setup uses a self-managed Kubernetes cluster and Helm.
- The tutorial requires ports 80 and 443 to be available for its example cluster setup.
- Istio is used for the documented SNI domain-routing feature.
- The repository warns that chaincode installation or building can fail on unsupported local Kubernetes versions and recommends KinD for testing.
- The README lists Hyperledger Fabric 2.3+ and 3.0 support; the repository description also lists 3.1.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Prepare a KinD cluster and install the operator
Create the tutorial's Kubernetes environment and install the Fabric operator and its custom resource definitions.
Before you start
- KinD and Helm installed
- Ports 80 and 443 available on the host
Steps
Create a KinD cluster using the tutorial configuration, which maps host ports 80 and 443 to cluster ports 30949 and 30950.
Add the KFS Helm chart repository.
Install the hlf-operator chart using the documented version 1.13.0 command.
Expected outcome
A Kubernetes cluster with the operator installed; the tutorial says the installation adds custom resource definitions for Fabric peers, orderers and authorities and deploys the controller.
Guide limitations
- The documented tutorial says its setup will not work if ports 80 or 443 are unavailable.
- This covers cluster preparation and operator installation, not deployment of a complete Fabric network.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 10 October 2026
- Original website title
- hyperledger-bevel/bevel-operator-fabric · Official homepage title · retained in its source language

