Update github file links to permalinks (#1086)

Signed-off-by: Roland Tyler <roland.tyler@consensys.net>
pull/1105/head
rolandtyler 2 years ago committed by GitHub
parent 12af7f46c7
commit 5356c40641
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
  1. 2
      docs/Concepts/Node-Types.md
  2. 2
      docs/Concepts/Privacy/Private-Transactions.md
  3. 2
      docs/HowTo/Configure/Consensus-Protocols/Clique.md
  4. 2
      docs/HowTo/Interact/APIs/GraphQL.md
  5. 6
      docs/HowTo/Monitor/Elastic-Stack.md
  6. 6
      docs/HowTo/Monitor/Logging.md
  7. 4
      docs/HowTo/Monitor/OpenTelemetry-Collector.md
  8. 2
      docs/HowTo/Monitor/Splunk-Enterprise.md
  9. 2
      docs/Reference/API-Methods.md
  10. 4
      docs/Reference/API-Objects.md
  11. 2
      docs/Reference/Accounts-for-Testing.md
  12. 2
      docs/Reference/Engine-API-Methods.md
  13. 2
      docs/Reference/Engine-API-Objects.md
  14. 2
      docs/Reference/Plugin-API-Interfaces.md
  15. 2
      docs/Tutorials/Contracts/Deploying-Contracts.md
  16. 6
      docs/Tutorials/Kubernetes/Create-Cluster.md
  17. 20
      docs/Tutorials/Kubernetes/Deploy-Charts.md
  18. 2
      docs/Tutorials/Kubernetes/Maintenance.md
  19. 6
      docs/Tutorials/Kubernetes/Overview.md
  20. 2
      docs/Tutorials/Kubernetes/Quorum-Explorer.md
  21. 2
      docs/Tutorials/Permissioning/Getting-Started-Onchain-Permissioning.md

@ -63,7 +63,7 @@ You can observe the `besu_synchronizer_fast_sync_*` and `besu_synchronizer_world
The failure has been seen on AWS and Digital Ocean.
On AWS, A full restart of the VM is required to restart the fast sync.
Fast sync isn't [currently supported on Digital Ocean](https://github.com/hyperledger/besu/blob/master/CHANGELOG.md#143).
Fast sync isn't [currently supported on Digital Ocean](https://github.com/hyperledger/besu/blob/750580dcca349d22d024cc14a8171b2fa74b505a/CHANGELOG.md#143).
!!! note

@ -127,6 +127,6 @@ You can manage private nonces in multiple ways:
!!! tip
The [web3js-quorum library includes an example](https://github.com/ConsenSys/web3js-quorum/blob/master/example/concurrentPrivateTransactions/concurrentPrivateTransactions.js)
The [web3js-quorum library includes an example](https://github.com/ConsenSys/web3js-quorum/blob/9a0f9eb1b91a4a0d93801f77782b509ae2e7314c/example/concurrentPrivateTransactions/concurrentPrivateTransactions.js)
of nonce management when [sending concurrent private transactions](../../HowTo/Send-Transactions/Concurrent-Private-Transactions.md).
The example calculates the correct nonces for the private transactions and PMTs outside of Besu.

@ -25,7 +25,7 @@ You can [create a private network using Clique](../../../Tutorials/Private-Netwo
To use Clique in a private network, Besu requires a Clique [genesis file](../Genesis-File.md). When connecting to Rinkeby,
Besu uses the
[`rinkeby.json`](https://github.com/hyperledger/besu/blob/master/config/src/main/resources/rinkeby.json)
[`rinkeby.json`](https://github.com/hyperledger/besu/blob/750580dcca349d22d024cc14a8171b2fa74b505a/config/src/main/resources/rinkeby.json)
genesis file in the `/besu/config/src/main/resources` directory.
A Clique genesis file defines properties specific to Clique.

@ -95,4 +95,4 @@ the [Besu GraphQL schema] from within the app.
```
<!-- Links -->
[Besu GraphQL schema]: https://github.com/hyperledger/besu/blob/master/ethereum/api/src/main/resources/schema.graphqls
[Besu GraphQL schema]: https://github.com/hyperledger/besu/blob/750580dcca349d22d024cc14a8171b2fa74b505a/ethereum/api/src/main/resources/schema.graphqls

@ -28,7 +28,7 @@ To see the Besu Quickstart network logs in Kibana:
![Kibana](../../images/KibanaQuickstart.png)
<!-- Links -->
[Filebeat]: https://github.com/ConsenSys/quorum-dev-quickstart/blob/master/files/common/filebeat/filebeat.yml
[Metricbeat]: https://github.com/ConsenSys/quorum-dev-quickstart/blob/master/files/common/metricbeat/metricbeat.yml
[pipeline configuration]: https://github.com/ConsenSys/quorum-dev-quickstart/blob/master/files/common/logstash/pipeline/20_besu.conf
[Filebeat]: https://github.com/ConsenSys/quorum-dev-quickstart/blob/b72a0f64d685c851bf8be399a8e33bbdf0e09982/files/common/filebeat/filebeat.yml
[Metricbeat]: https://github.com/ConsenSys/quorum-dev-quickstart/blob/b72a0f64d685c851bf8be399a8e33bbdf0e09982/files/common/metricbeat/metricbeat.yml
[pipeline configuration]: https://github.com/ConsenSys/quorum-dev-quickstart/blob/b72a0f64d685c851bf8be399a8e33bbdf0e09982/files/common/logstash/pipeline/20_besu.conf
[Elastic Stack]: https://www.elastic.co/what-is/elk-stack

@ -76,6 +76,6 @@ For Bash-based executions, you can set the variable for only the scope of the pr
[log rotation to restrict the size of the log files].
<!-- Links -->
[default configuration]: https://github.com/hyperledger/besu/blob/master/besu/src/main/resources/log4j2.xml
[log rotation to restrict the size of the log files]: https://github.com/ConsenSys/quorum-dev-quickstart/blob/master/files/besu/config/besu/log-config.xml
[default configuration]: https://github.com/hyperledger/besu/blob/master/besu/src/main/resources/log4j2.xml
[default configuration]: https://github.com/hyperledger/besu/blob/750580dcca349d22d024cc14a8171b2fa74b505a/besu/src/main/resources/log4j2.xml
[log rotation to restrict the size of the log files]: https://github.com/ConsenSys/quorum-dev-quickstart/blob/b72a0f64d685c851bf8be399a8e33bbdf0e09982/files/besu/config/besu/log-config.xml
[default configuration]: https://github.com/hyperledger/besu/blob/750580dcca349d22d024cc14a8171b2fa74b505a/besu/src/main/resources/log4j2.xml

@ -138,7 +138,7 @@ Download and install the [OpenTelemetry Collector](https://github.com/open-telem
otel/opentelemetry-collector-contrib:latest
```
You can also refer to this [Docker-compose example](https://github.com/splunk/splunk-connect-for-ethereum/blob/master/examples/besu-sync/full-sync/docker-compose.yaml).
You can also refer to this [Docker-compose example](https://github.com/splunk/splunk-connect-for-ethereum/blob/989dc2ccae7d8235bf3ce2a83a18cf0cd1713294/examples/besu-sync/full-sync/docker-compose.yaml).
1. Start Besu with the [`--metrics-enabled`](../../Reference/CLI/CLI-Syntax.md#metrics-enabled) and
[`--metrics-protocol=opentelemetry`](../../Reference/CLI/CLI-Syntax.md#metrics-protocol) options.
@ -156,7 +156,7 @@ Download and install the [OpenTelemetry Collector](https://github.com/open-telem
OTEL_EXPORTER_OTLP_ENDPOINT=https://localhost:4317 besu --network=dev --miner-enabled --miner-coinbase fe3b557e8fb62b89f4916b721be55ceb828dbd73 --rpc-http-cors-origins="all" --rpc-http-enabled --metrics-enabled --metrics-protocol=opentelemetry
```
The [OpenTelemetry SDK](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/sdk-environment-variables.md)
The [OpenTelemetry SDK](https://github.com/open-telemetry/opentelemetry-specification/blob/8f7cdb73618a0b3afa9532b8f8103d719e352781/specification/sdk-environment-variables.md)
mandates how to configure the OpenTelemetry gRPC client, so data flows to the collector from Besu.
You can use the following environment variables:

@ -68,7 +68,7 @@ Docker Compose environment provided by Splunk.
### Requirements
- [Docker](https://docs.docker.com/compose/install/)
- [Besu 1.4.4](https://github.com/hyperledger/besu/blob/master/CHANGELOG.md#144) or later [installed](../Get-Started/Installation-Options/Install-Binaries.md)
- [Besu 1.4.4](https://github.com/hyperledger/besu/blob/750580dcca349d22d024cc14a8171b2fa74b505a/CHANGELOG.md#144) or later [installed](../Get-Started/Installation-Options/Install-Binaries.md)
!!! important

@ -8112,7 +8112,7 @@ None
```
<!-- Links -->
[schema]: https://github.com/hyperledger/besu/blob/master/ethereum/api/src/main/resources/schema.graphqls
[schema]: https://github.com/hyperledger/besu/blob/750580dcca349d22d024cc14a8171b2fa74b505a/ethereum/api/src/main/resources/schema.graphqls
[eth_sendRawTransaction or eth_call]: ../HowTo/Send-Transactions/Transactions.md#eth_call-or-eth_sendrawtransaction
[transaction]: https://ropsten.etherscan.io/tx/0xfc766a71c406950d4a4955a340a092626c35083c64c7be907060368a5e6811d6
[add or remove a signer with the specified address]: ../HowTo/Configure/Consensus-Protocols/Clique.md#add-and-remove-signers

@ -32,7 +32,7 @@ Returned by [`eth_getBlockByHash`](API-Methods.md#eth_getblockbyhash) and
| **timestamp** | Quantity | Unix timestamp for block assembly. |
| **transactions** | Array | Array of [transaction objects](#transaction-object), or 32 byte transaction hashes depending on the specified boolean parameter. |
| **uncles** | Array | Array of uncle hashes. |
| **baseFeePerGas** | Quantity | The block's [base fee per gas](../Concepts/Transactions/Transaction-Types.md#eip1559-transactions). This field is empty for blocks created before [EIP-1559](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1559.md). |
| **baseFeePerGas** | Quantity | The block's [base fee per gas](../Concepts/Transactions/Transaction-Types.md#eip1559-transactions). This field is empty for blocks created before [EIP-1559](https://github.com/ethereum/EIPs/blob/2d8a95e14e56de27c5465d93747b0006bd8ac47f/EIPS/eip-1559.md). |
## Fee history results object
@ -42,7 +42,7 @@ If blocks in the specified block range are not available, then only the fee hist
| Key | Type | Value |
|-----|:----:|-------|
| **oldestBlock** | Quantity, Integer | Lowest number block of the returned range. |
| **baseFeePerGas** | Array | Array of block base fees per gas, including an extra block value. The extra value is the next block after the newest block in the returned range. Returns zeroes for blocks created before [EIP-1559](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1559.md). |
| **baseFeePerGas** | Array | Array of block base fees per gas, including an extra block value. The extra value is the next block after the newest block in the returned range. Returns zeroes for blocks created before [EIP-1559](https://github.com/ethereum/EIPs/blob/2d8a95e14e56de27c5465d93747b0006bd8ac47f/EIPS/eip-1559.md). |
| **gasUsedRatio** | Array | Array of block gas used ratios. These are calculated as the ratio of `gasUsed` and `gasLimit`. |
## Filter options object

@ -20,7 +20,7 @@ The `dev.json` genesis file defines the following accounts used for testing.
To use existing test accounts, specify the accounts and balances in a genesis file for your test
network. For an example of how to define accounts in the genesis file, see
[`dev.json`](https://github.com/hyperledger/besu/blob/master/config/src/main/resources/dev.json).
[`dev.json`](https://github.com/hyperledger/besu/blob/750580dcca349d22d024cc14a8171b2fa74b505a/config/src/main/resources/dev.json).
To start Besu with the genesis file defining the existing accounts, use the
[`--genesis-file`](CLI/CLI-Syntax.md#genesis-file) command line option .

@ -7,7 +7,7 @@ description: Engine API methods reference
After [The Merge](../Concepts/Merge.md), consensus and execution clients communicate with each other using the Engine API.
When running Besu as an execution client, [use these API calls](../HowTo/Interact/APIs/Engine-API.md) to communicate with a consensus client.
See the [Ethereum Engine API specification](https://github.com/ethereum/execution-apis/blob/main/src/engine/specification.md) for more information.
See the [Ethereum Engine API specification](https://github.com/ethereum/execution-apis/blob/0b965fb714ccd3faa3c939fdce1726e56679cdec/src/engine/specification.md) for more information.
## Methods

@ -24,7 +24,7 @@ Returned by [`engine_getPayloadV1`](Engine-API-Methods.md#engine_getpayloadv1).
| `gasUsed` | *Quantity*, 64 Bits | Total gas used by all transactions in this block. |
| `timestamp` | *Quantity*, 64 Bits | Unix timestamp for block assembly. |
| `extraData` | *Data*, 0 to 32 Bytes | Extra data field for this block. |
| `baseFeePerGas` | *Quantity*, 256 Bits | The block's [base fee per gas](../Concepts/Transactions/Transaction-Types.md#eip1559-transactions). This field is empty for blocks created before [EIP-1559](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1559.md). |
| `baseFeePerGas` | *Quantity*, 256 Bits | The block's [base fee per gas](../Concepts/Transactions/Transaction-Types.md#eip1559-transactions). This field is empty for blocks created before [EIP-1559](https://github.com/ethereum/EIPs/blob/2d8a95e14e56de27c5465d93747b0006bd8ac47f/EIPS/eip-1559.md). |
| `blockHash` | *Data*, 32 Bytes | Hash of the execution block. |
| `transactions` | *Array* | Array of transaction objects, each object is a list representing `TransactionType`, `TransactionPayload`, or `LegacyTransaction` as defined in [EIP-2718](https://eips.ethereum.org/EIPS/eip-2718). |

@ -44,7 +44,7 @@ The following table lists interfaces providing services you can retrieve.
| [**RpcEndpointService**](https://wiki.hyperledger.org/display/BESU/RpcEndpointService) | Register custom RPC endpoints. |
To use the interfaces in your plugin, ensure the
[Gradle build file](https://github.com/ConsenSys/PluginsAPIDemo/blob/master/build.gradle) contains
[Gradle build file](https://github.com/ConsenSys/PluginsAPIDemo/blob/957628b3c6f533f3c3f405e2a17e369cd1f02c31/build.gradle) contains
the `https://hyperledger.jfrog.io/hyperledger/besu-maven` repository and the `plugin-api` dependency.
!!! warning "Known issue"

@ -249,7 +249,7 @@ the contract's address.
* Specify the `privacyGroupId` instead of the `privateFor` option in the txOptions above and then send the transaction.
The Developer Quickstart provides an
[example of a private transaction with a privacy group](https://github.com/ConsenSys/quorum-dev-quickstart/blob/master/files/besu/smart_contracts/scripts/private_tx_privacy_group.js).
[example of a private transaction with a privacy group](https://github.com/ConsenSys/quorum-dev-quickstart/blob/b72a0f64d685c851bf8be399a8e33bbdf0e09982/files/besu/smart_contracts/privacy/scripts/private_tx_privacy_group.js).
## Using `eea_sendRawTransaction` for private contracts with web3js-eea

@ -109,7 +109,7 @@ exhaustion as your application demands grow, however makes it easier for externa
To provision the cluster:
1. Update [cluster.yml](https://github.com/ConsenSys/quorum-kubernetes/blob/master/aws/templates/cluster.yml)
1. Update [cluster.yml](https://github.com/ConsenSys/quorum-kubernetes/blob/5920caff6dd15b4ca17f760ad9e4d7d2e43b41a1/aws/templates/cluster.yml)
1. Deploy the template:
@ -249,12 +249,12 @@ To provision the cluster:
1. Search for `Template deployment (deploy using custom templates)` and select **Create**.
1. Select **Build your own template in the editor**.
1. Remove the contents (JSON) in the editor and paste in the contents of
[`azuredeploy.json`](https://github.com/ConsenSys/quorum-kubernetes/blob/master/azure/arm/azuredeploy.json)
[`azuredeploy.json`](https://github.com/ConsenSys/quorum-kubernetes/blob/5920caff6dd15b4ca17f760ad9e4d7d2e43b41a1/azure/arm/azuredeploy.json)
1. Select **Save**.
1. Input provisioning parameters in the displayed user interface.
1. Provision the drivers:
1. Run the [bootstrap](https://github.com/ConsenSys/quorum-kubernetes/blob/master/azure/scripts/bootstrap.sh) script.
1. Run the [bootstrap](https://github.com/ConsenSys/quorum-kubernetes/blob/5920caff6dd15b4ca17f760ad9e4d7d2e43b41a1/azure/scripts/bootstrap.sh) script.
1. Use `besu` for `AKS_NAMESPACE`, and update `AKS_RESOURCE_GROUP`, `AKS_CLUSTER_NAME`, and `AKS_MANAGED_IDENTITY`
in the commands below to match your settings and deployed resources from step 3.

@ -100,7 +100,7 @@ kubectl create namespace besu
This chart deploys Prometheus and Grafana to monitor the metrics of the cluster, nodes and state of the network.
Update the admin `username` and `password` in the [monitoring values file](https://github.com/ConsenSys/quorum-kubernetes/blob/master/helm/values/monitoring.yml). Configure alerts to the receiver of your choice (for example, email or Slack), then deploy the chart using:
Update the admin `username` and `password` in the [monitoring values file](https://github.com/ConsenSys/quorum-kubernetes/blob/5920caff6dd15b4ca17f760ad9e4d7d2e43b41a1/helm/values/monitoring.yml). Configure alerts to the receiver of your choice (for example, email or Slack), then deploy the chart using:
```bash
helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
@ -110,7 +110,7 @@ kubectl --namespace besu apply -f ./values/monitoring/
```
Metrics are collected via a
[ServiceMonitor](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides/getting-started.md)
[ServiceMonitor](https://github.com/prometheus-operator/prometheus-operator/blob/7c77626e5e270a2530e187b185d45eeed8a773bf/Documentation/user-guides/getting-started.md)
that scrapes each Besu pod, using given
[`annotations`](https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/) which specify the
port and path to use. For example:
@ -200,7 +200,7 @@ The genesis chart creates the genesis file and keys for the validators.
`validator-n`, where `n` is the node number. Any validators created after the initial pool can be named
to anything you like.
The override [values.yml](https://github.com/ConsenSys/quorum-kubernetes/blob/master/helm/values/genesis-besu.yml)
The override [values.yml](https://github.com/ConsenSys/quorum-kubernetes/blob/5920caff6dd15b4ca17f760ad9e4d7d2e43b41a1/helm/values/genesis-besu.yml)
looks like below:
```bash
@ -353,7 +353,7 @@ are proposed and created on the chain.
These are the next set of nodes that we will deploy. The charts use four validators (default) to replicate best practices
for a network. The override
[values.yml](https://github.com/ConsenSys/quorum-kubernetes/blob/master/helm/values/validator.yml) for the
[values.yml](https://github.com/ConsenSys/quorum-kubernetes/blob/5920caff6dd15b4ca17f760ad9e4d7d2e43b41a1/helm/values/validator.yml) for the
StatefulSet looks like below:
```bash
@ -412,7 +412,7 @@ An RPC node is simply a node that can be used to make public transactions or per
as when connected to a chain explorer like [BlockScout](https://github.com/blockscout/blockscout).
The RPC override
[values.yml](https://github.com/ConsenSys/quorum-kubernetes/blob/master/helm/values/reader.yml) for the
[values.yml](https://github.com/ConsenSys/quorum-kubernetes/blob/5920caff6dd15b4ca17f760ad9e4d7d2e43b41a1/helm/values/reader.yml) for the
StatefulSet looks identical to that of the validators above, and will create it's own node keys before the node starts.
To deploy an RPC node:
@ -425,7 +425,7 @@ A Transaction or Member node in turn is one which has an accompanying Private Tr
which allow you to make private transactions between nodes.
The Transaction override
[values.yml](https://github.com/ConsenSys/quorum-kubernetes/blob/master/helm/values/txnode.yml) for the
[values.yml](https://github.com/ConsenSys/quorum-kubernetes/blob/5920caff6dd15b4ca17f760ad9e4d7d2e43b41a1/helm/values/txnode.yml) for the
StatefulSet looks identical to that of the validators above and only has `quorumFlags.privacy: true` to indicate that
it is deploying a pair of GoQuorum and Tessera nodes.
@ -467,10 +467,10 @@ helm install quorum-network-ingress ingress-nginx/ingress-nginx \
--set controller.service.externalTrafficPolicy=Local
```
Use [pre-defined rules](https://github.com/ConsenSys/quorum-kubernetes/blob/master/ingress/ingress-rules-besu.yml)
Use [pre-defined rules](https://github.com/ConsenSys/quorum-kubernetes/blob/5920caff6dd15b4ca17f760ad9e4d7d2e43b41a1/ingress/ingress-rules-besu.yml)
to test functionality, and alter to suit your requirements (for example, restrict access for API calls to trusted CIDR blocks).
Edit the [rules](https://github.com/ConsenSys/quorum-kubernetes/blob/master/ingress/ingress-rules-besu.yml) file so that the
Edit the [rules](https://github.com/ConsenSys/quorum-kubernetes/blob/5920caff6dd15b4ca17f760ad9e4d7d2e43b41a1/ingress/ingress-rules-besu.yml) file so that the
service names match your release name. In the example, we deployed a transaction node with the release name `member-1`
so the corresponding service is called `besu-node-member-1`. Once you have settings
that match your deployments, deploy the rules as follows:
@ -505,7 +505,7 @@ The following is an example RPC call, which confirms that the node running the J
### 10. Blockchain explorer
You can deploy [BlockScout](https://github.com/blockscout/blockscout) to aid with monitoring the blockchain.
To do this, update the [BlockScout values file](https://github.com/ConsenSys/quorum-kubernetes/blob/master/helm/values/blockscout-besu.yml)
To do this, update the [BlockScout values file](https://github.com/ConsenSys/quorum-kubernetes/blob/5920caff6dd15b4ca17f760ad9e4d7d2e43b41a1/helm/values/blockscout-besu.yml)
and set the `database` and `secret_key_base` values.
!!! important
@ -532,7 +532,7 @@ to use the application.
The accounts listed in the file below are for test purposes only and should not be used on a production network.
To deploy the application, update the
[Explorer values file](https://github.com/ConsenSys/quorum-kubernetes/blob/master/helm/values/explorer-besu.yaml)
[Explorer values file](https://github.com/ConsenSys/quorum-kubernetes/blob/5920caff6dd15b4ca17f760ad9e4d7d2e43b41a1/helm/values/explorer-besu.yaml)
with details of your nodes and endpoints and then deploy.
```bash

@ -19,7 +19,7 @@ Production charts for Azure use Azure Files, and on AWS use EBS Block Store whic
To update the volume size, you must update the override values file.
For example, to increase the size on the transaction nodes volumes, add the following snippet to the
[`txnode values.yml`](https://github.com/ConsenSys/quorum-kubernetes/blob/master/helm/values/txnode.yml) file, with
[`txnode values.yml`](https://github.com/ConsenSys/quorum-kubernetes/blob/5920caff6dd15b4ca17f760ad9e4d7d2e43b41a1/helm/values/txnode.yml) file, with
the new size limit (the following example uses 50Gi).
```bash

@ -41,7 +41,7 @@ Secrets, and will also make use of AWS IAM or Azure Managed Identities for the p
The repository's `helm` charts support on-premise and cloud providers such as AWS, Azure, GCP, IBM etc. You can
configure the provider in the
[values.yml](https://github.com/ConsenSys/quorum-kubernetes/blob/master/helm/values/genesis-besu.yml) file of
[values.yml](https://github.com/ConsenSys/quorum-kubernetes/blob/5920caff6dd15b4ca17f760ad9e4d7d2e43b41a1/helm/values/genesis-besu.yml) file of
the respective charts by setting `cluster.provider` to `local`, `aws`, or `azure`. If you use
GCP, IBM etc., please set `cluster.provider: local` and `cluster.cloudNativeServices: false`.
@ -125,7 +125,7 @@ Select the appropriate type of [Storage Class](https://kubernetes.io/docs/concep
on your cloud provider. In the templates, the size of the [volume claims](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims)
is set to 20Gb by default; you can change this depending on your needs. If you have a different storage
account than the one in the charts, you may edit those
[storageClasses](https://github.com/ConsenSys/quorum-kubernetes/blob/master/helm/charts/besu-node/templates/node-storage.yaml).
[storageClasses](https://github.com/ConsenSys/quorum-kubernetes/blob/5920caff6dd15b4ca17f760ad9e4d7d2e43b41a1/helm/charts/besu-node/templates/node-storage.yaml).
When using PVCs, set the `allowVolumeExpansion` to `true`. This helps keep costs low and enables growing the volume
over time rather than creating new volumes and copying data across.
@ -167,6 +167,6 @@ helm install filebeat --version 7.17.1 elastic/filebeat --namespace besu --valu
### Ingress Controllers
If you require the ingress controllers for the RPC calls or the monitoring dashboards, we have provided example
[rules](https://github.com/ConsenSys/quorum-kubernetes/blob/master/ingress/ingress-rules-besu.yml) that
[rules](https://github.com/ConsenSys/quorum-kubernetes/blob/5920caff6dd15b4ca17f760ad9e4d7d2e43b41a1/ingress/ingress-rules-besu.yml) that
are pre-configured for common use cases. Use these as a reference and develop solutions to match your network
topology and requirements.

@ -21,7 +21,7 @@ The explorer can provide an overview over the whole network, such as block infor
validators from the network, and demonstrates using the `SimpleStorage` smart contract with privacy enabled, and sending
transactions between wallets in one interface.
To use the explorer, update the [Quorum-Explorer values file](https://github.com/ConsenSys/quorum-kubernetes/blob/master/helm/values/explorer-besu.yaml)
To use the explorer, update the [Quorum-Explorer values file](https://github.com/ConsenSys/quorum-kubernetes/blob/5920caff6dd15b4ca17f760ad9e4d7d2e43b41a1/helm/values/explorer-besu.yaml)
with your node details and endpoints, and then [deploy](./Deploy-Charts.md).
## Nodes

@ -151,7 +151,7 @@ Copy the `genesis.json` file to the `Permisssioned-Network` directory.
contract to the genesis file.
Add the Ingress contracts to the genesis file for your network by copying them from
[`genesis.json`](https://github.com/ConsenSys/permissioning-smart-contracts/blob/master/genesis.json)
[`genesis.json`](https://github.com/ConsenSys/permissioning-smart-contracts/blob/e6c2d4d5a728c11cdb8e97a07ddda3c0bfb57b5d/genesis.json)
in the [`permissioning-smart-contracts` repository](https://github.com/ConsenSys/permissioning-smart-contracts) to
the `alloc` section of the contract:

Loading…
Cancel
Save