Quorum Charts¶

The structure below represents the Chart structure for Quorum components in Hyperledger Bevel implementation.

/quorum
|-- charts
|   |-- node_constellation
|   |-- node_tessera

Pre-requisites¶

helm to be installed and configured on the cluster.

node_constellation¶

About¶

This chart is used to deploy Quorum nodes with constellation transaction manager.

Folder Structure¶

/node_constellation
|-- templates
|   |-- _helpers.tpl
|   |-- configmap.yaml
|   |-- ingress.yaml
|   |-- deployment.yaml
|   |-- service.yaml
|-- Chart.yaml
|-- values.yaml

Charts description¶

templates¶

This folder contains template structures which, when combined with values, will generate valid Kubernetes manifest files for auth job implementation.
This folder contains following template files for node_constellation implementation
- _helpers.tpl
  
  This file doesn’t output a Kubernetes manifest file as it begins with underscore (_). And it’s a place to put template helpers that we can re-use throughout the chart. That file is the default location for template partials, as we have defined a template to encapsulate a Kubernetes block of labels for node_constellation.
- deployment.yaml
  
  This file is used as a basic manifest for creating a Kubernetes deployment. For the node_constellation, this file creates a constellation node deployment deployment. The file defines 3 containers, init container which gets all the secrets from the vault, constellation node container and a quorum container.
- service.yaml
  
  This template is used as a basic manifest for creating a service endpoint for our deployment. The file basically specifies service type and kind of service ports for the constellation node.
- configmap.yaml
  
  The ConfigMap API resource provides mechanisms to inject containers with configuration data while keeping containers agnostic of Kubernetes. Here it is used to store Genesis Data.
- ingress.yaml
  
  Ingress exposes HTTP and HTTPS routes from outside the cluster to services within the cluster. Traffic routing is controlled by rules defined on the Ingress resource. This file containes those resources.

Chart.yaml¶

This file contains the information about the chart such as apiversion, appversion, name, etc.

values.yaml¶

This file contains the default configuration values for the chart.

node_tessera¶