You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/guides/fabric/deploy-operations-console.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,7 @@
14
14
## Prerequisites
15
15
The [Fabric Operations Console](https://github.com/hyperledger-labs/fabric-operations-console) can be deployed along with the Fabric Network.
16
16
You can then manually add peers, orderers, CA to the console by importing appropriate JSON files.
17
+
Bevel deploys the console together with the required `fabric-deployer` sidecar so channel and ordering-service workflows can use the backend deployer APIs out of the box.
17
18
18
19
The Helm Chart for Fabric Operations Console is available [here](https://github.com/hyperledger/bevel/blob/main/platforms/hyperledger-fabric/charts/fabric-operations-console).
Copy file name to clipboardExpand all lines: platforms/hyperledger-fabric/charts/fabric-operations-console/README.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,9 +57,9 @@ operation_console/
57
57
-`templates/`: Contains the Kubernetes manifest templates that define the resources to be deployed.
58
58
-`helpers.tpl`: Contains custom label definitions used in other templates.
59
59
-`configmap.yaml`: Store configuration for the fabric-console
60
-
-`deployment.yaml`: Defines a StatefulSet with one replica that manages three containers: couchdb, fabric-console, and configtxlator. The couchdb container will be used to store the data for the Fabric network and it will be exposed on port 5984. The fabric-console container will be used to interact with the Fabric network and it will be exposed on port 3000. The configtxlator container will be used to generate and manage configuration transactions for the Fabric network and it will be exposed on port 7059.
60
+
-`deployment.yaml`: Defines a StatefulSet with one replica that manages four containers: couchdb, fabric-console, fabric-deployer, and configtxlator. The couchdb container will be used to store the data for the Fabric network and it will be exposed on port 5984. The fabric-console container will be used to interact with the Fabric network and it will be exposed on port 3000. The fabric-deployer sidecar provides the backend APIs the console uses for orderer and channel workflows and listens on port 8080 inside the pod. The configtxlator container will be used to generate and manage configuration transactions for the Fabric network and it will be exposed on port 7059.
61
61
-`pvc.yaml`: Defines a persistent volume claim that will be used to store the data for the CouchDB database.
62
-
-`service.yaml`: configures a Kubernetes Service and an Ingress. The service has three ports: console (port 3000) is exposed for the fabric-console, couchdb (port 5984) is exposed for the couchdb database, and configtxlator (port 7059) is exposed for the configtxlator container. The service can be exposed in two ways: ClusterIP and NodePort. Optionally, if haproxy is selected, ingress will route traffic to the Service using the host and path.
62
+
-`service.yaml`: configures a Kubernetes Service and an Ingress. The service has three externally exposed ports: console (port 3000) is exposed for the fabric-console, couchdb (port 5984) is exposed for the couchdb database, and configtxlator (port 7059) is exposed for the configtxlator container. The fabric-deployer sidecar is only used from inside the pod by the console. The service can be exposed in two ways: ClusterIP and NodePort. Optionally, if haproxy is selected, ingress will route traffic to the Service using the host and path.
63
63
-`Chart.yaml`: Contains the metadata for the Helm chart, such as the name, version, and description.
64
64
-`README.md`: Provides information and instructions about the Helm chart.
65
65
-`values.yaml`: Contains the default configuration values for the Helm chart.
@@ -77,6 +77,7 @@ The [values.yaml](https://github.com/hyperledger/bevel/blob/develop/platforms/hy
77
77
| namespace | Provide the namespace for organization's peer | org1-net |
78
78
| images.couchdb | Valid image name and version for fabric couchdb | couchdb:3.1.1 |
79
79
| images.console | Valid image name and version for fabric operations console | ghcr.io/hyperledger-labs/fabric-console:latest|
80
+
| images.deployer | Valid image name and version for the fabric deployer sidecar | ghcr.io/ibm-blockchain/fabric-deployer:latest-amd64|
80
81
| images.configtxlator | Valid image name and version to read certificates from vault server | ghcr.io/hyperledger/bevel-fabric-tools:2.2.2 |
0 commit comments