local/fabric-x-cryptogen.yaml¶
fabric-x-cryptogen.yaml runs the local container topology without Fabric CA services. Crypto material is generated on the control node with cryptogen.
Use it for fast, repeatable local tests where Fabric CA enrollment is not under test.
Warning
This inventory is intended for debugging and repeatable test runs. For production-style deployments, start from the Fabric CA based local/fabric-x.yaml inventory instead.
Network Diagram¶
The diagram below summarizes this inventory's Fabric-X services and how they fit together.

Inventory Details¶
The Fabric-X services, PostgreSQL, load generator, and monitoring stack run as local containers. cryptogen runs on the control node and writes artifacts below cryptogen_artifacts_dir.
This inventory deploys these logical services on the local machine:
- No Fabric CA servers or Fabric CA databases.
- 4 orderer groups. Each group has 1 router, 1 consenter, 1 assembler, and 1 batcher.
- 1 committer with validator, verifier, coordinator, sidecar, query service, and PostgreSQL storage.
- 1 Block Explorer server and UI with PostgreSQL storage, streaming blocks from the committer sidecar.
- 1 load generator.
- Monitoring with node exporter, PostgreSQL exporter, cAdvisor, Prometheus, Grafana, Loki, and Alloy.
flowchart TD
all --> network
network --> fabric_x
all --> load_generators
all --> monitoring
monitoring --> prometheus
monitoring --> grafana
monitoring --> loki
monitoring --> alloy
monitoring --> node_exporter
monitoring --> postgres_exporter
monitoring --> cadvisor
grafana --> prometheus
grafana --> loki
alloy --> loki
prometheus --> node_exporter
prometheus --> postgres_exporter
prometheus --> cadvisor
fabric_x --> fabric_x_orderers
fabric_x --> fabric_x_committers
fabric_x --> fabric_x_block_explorer
fabric_x_committers --> fabric_x_committer
fabric_x_orderers --> fabric_x_orderer_1
fabric_x_orderers --> fabric_x_orderer_2
fabric_x_orderers --> fabric_x_orderer_3
fabric_x_orderers --> fabric_x_orderer_4
Fabric CA is omitted entirely. Certificates and keys are generated centrally before the local container services consume them.