Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[quorum] introduce helm chart deployment capability #2512

Merged

Conversation

saurabhkumarkardam
Copy link
Contributor

@saurabhkumarkardam saurabhkumarkardam commented Feb 20, 2024

Commit to be reviewed


feat(quorum): introduce helm chart deployment capability

This commit enhances the deployment process for the Quorum Distributed Ledger Technology (DLT) network by exclusively leveraging Helm charts.

Four new Helm charts have been introduced to streamline the deployment process:
1. quorum-genesis: Initializes the network with specific requirements.
2. quorum-node: Starts the network and allows adding new nodes.
3. quorum-tessera-node: Facilitates privacy by enabling transaction encryption using Tessera.
4. quorum-tlscert-gen: Enables secure access to the node via HTTPS.

Each chart comes with a README to help users customize the network.

These changes make deploying and managing the Quorum DLT network smoother with Helm.

Other Improvements:
1. Added error handling to ensure clean uninstallation of the besu-genesis and besu-tlscert-gen charts.
2. Updated the README's API Call section.

fixes #2484

Copy link
Contributor

@sownak sownak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

More comments after these but most are common changes for all files

platforms/hyperledger-besu/charts/README.md Show resolved Hide resolved
platforms/quorum/charts/README.md Outdated Show resolved Hide resolved
platforms/quorum/charts/README.md Outdated Show resolved Hide resolved
platforms/quorum/charts/README.md Outdated Show resolved Hide resolved
platforms/quorum/charts/quorum-genesis/values.yaml Outdated Show resolved Hide resolved
Copy link
Contributor

@suvajit-sarkar suvajit-sarkar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@saurabhkumarkardam saurabhkumarkardam force-pushed the goquorum-2484 branch 2 times, most recently from 71f3851 to e19c40c Compare March 4, 2024 06:56
This commit enhances the deployment process for the Quorum Distributed Ledger Technology (DLT) network by exclusively leveraging Helm charts.

Four new Helm charts have been introduced to streamline the deployment process:
1. quorum-genesis: Initializes the network with specific requirements.
2. quorum-node: Starts the network and allows adding new nodes.
3. quorum-tessera-node: Facilitates privacy by enabling transaction encryption using Tessera.
4. quorum-tlscert-gen: Enables secure access to the node via HTTPS.

Each chart comes with a README to help users customize the network.

These changes make deploying and managing the Quorum DLT network smoother with Helm.

Other Improvements:
- Added error handling to ensure clean uninstallation of the besu-genesis and besu-tlscert-gen charts.
- Updated the README's API Call section.

fixes hyperledger-bevel#2484

Signed-off-by: saurabhkumarkardam <[email protected]>
@suvajit-sarkar suvajit-sarkar merged commit 0b004fa into hyperledger-bevel:develop Mar 4, 2024
3 checks passed
@@ -145,4 +169,5 @@ To deploy the proposed validator chart, we need to deploy the Besu node chart fi

```bash
helm install validator-5 ./besu-propose-validator --namespace supplychain-bes --values besu-propose-validator/values.yaml
>>>>>>> upstream/develop
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bad merge

memory: "{{ .Values.node.goquorum.resources.memLimit }}"
volumeMounts:
- name: static-nodes
mountPath: /{{ .Release.Name }}/staticNode/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't think the mountpaths should have variables. Just because it was done previously does not make it right. Please use static paths.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants