k8s/fabric-x-cryptogen.yaml

fabric-x-cryptogen.yaml deploys the Kubernetes sample without Fabric CA services. Crypto material is generated on the control node with cryptogen.

Use it for repeatable Kubernetes tests that should not exercise Fabric CA enrollment.

Warning

This inventory is intended for debugging and repeatable test runs. For production-style deployments, start from the Fabric CA based k8s/fabric-x.yaml inventory instead.

Network Diagram

The diagram below summarizes this inventory's Fabric-X services and how they fit together.

Inventory Details

Orderer, committer, PostgreSQL, load generator, node exporter, Prometheus, and Grafana use Kubernetes task paths. cryptogen runs on the control node and writes artifacts below cryptogen_artifacts_dir.

This inventory deploys these logical services as Kubernetes workloads and services:

• 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 load generator.
• Monitoring with node exporter, PostgreSQL exporter, Prometheus, and Grafana.

flowchart TD
  all --> control_node_crypto["cryptogen artifacts"]
  all --> network
  network --> fabric_x
  all --> load_generators
  all --> monitoring
  fabric_x --> fabric_x_orderers
  fabric_x --> fabric_x_committer
  fabric_x_orderers --> orderer_groups["fabric_x_orderer_1..4"]
  fabric_x_committer --> committer_services["validator, verifier, coordinator, sidecar, query service"]
  fabric_x_committer --> committer_db["committer-db PostgreSQL"]
  control_node_crypto -.-> fabric_x_orderers
  control_node_crypto -.-> fabric_x_committer

Fabric CA is omitted entirely. Certificates and keys are generated centrally before Kubernetes-backed component configuration consumes them.