openshift/fabric-x.yaml¶

fabric-x.yaml is the default OpenShift sample. It deploys a complete Fabric-X network with Fabric CA, PostgreSQL, TLS, mTLS, and OpenShift Route exposure.

Use it as the baseline when validating OpenShift workloads, services, storage, and externally reachable endpoints. Fabric CA servers are exposed via OpenShift Routes instead of Kubernetes NodePorts.

Network Diagram¶

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

OpenShift Fabric-X inventory

Inventory Details¶

Fabric CA, CA databases, orderer, committer, PostgreSQL, load generator, node exporter, Prometheus, and Grafana use OpenShift task paths. Ansible still runs from the control node, but inventory hosts represent OpenShift resources rather than SSH machines.

This inventory deploys these logical services as OpenShift workloads, services, and routes:

5 Fabric CA servers and 5 PostgreSQL databases for Fabric CA state.
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.

Note

If you run on macOS, the OpenShift routes map to 127.0.0.1. While this works fine with binary CLIs, it can break containerized binaries because 127.0.0.1 is then resolved inside the container network namespace. Run make oc-config-hosts-on-macos (requires sudo) to setup the routes in /etc/hosts before starting Fabric-X.

flowchart TD
  all --> network
  network --> fabric_cas
  network --> fabric_x
  all --> load_generators
  all --> monitoring
  fabric_cas --> fabric_ca_servers
  fabric_cas --> fabric_ca_dbs
  fabric_x --> fabric_x_orderers
  fabric_x --> fabric_x_committers
  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

This is the OpenShift equivalent of the default Kubernetes inventory. External-facing services use OpenShift Routes, while internal services stay behind ClusterIP services.