-
Notifications
You must be signed in to change notification settings - Fork 27
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Showing
6 changed files
with
60 additions
and
172 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,54 +1,66 @@ | ||
# Operator Helm Chart | ||
|
||
Kubernetes Helm chart for deploying v3-operator. | ||
This Helm chart allows you to deploy the StakeWise v3-operator into a Kubernetes cluster. The v3-operator plays a vital role in the StakeWise ecosystem, and this Helm chart aims to simplify its deployment. | ||
|
||
## Introduction | ||
|
||
Can be used to deploy StakeWise operator on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager. | ||
The StakeWise v3-operator can be deployed on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager. This document provides step-by-step instructions for installation, configuration, and management of the Helm chart. | ||
|
||
## Prerequisites | ||
|
||
- Kubernetes 1.19+ | ||
Before you start, make sure your environment meets the following prerequisites: | ||
|
||
- Kubernetes 1.20 or higher | ||
- Helm 3 | ||
- Operator data created as Kubernetes secrets | ||
|
||
## Installing the Chart | ||
## Create Kubernetes secrets with operator data | ||
|
||
To install the chart with the release name `my-release`: | ||
Kubernetes secrets are used to store sensitive information related to the v3-operator. Use the following commands to create the necessary secrets: | ||
|
||
```bash | ||
$ helm repo add stakewise https://charts.stakewise.io | ||
$ kubectl create secret generic keystores --from-file=keystores/ | ||
$ helm install my-release --set settings.network="goerli" stakewise/v3-operator | ||
kubectl create secret generic v3-operator-deposit-data --from-file=/home/username/.stakewise/0xeefffd4c23d2e8c845870e273861e7d60df49663/deposit_data.json | ||
kubectl create secret generic v3-operator-keystores-data --from-file=/home/username/.stakewise/0xeefffd4c23d2e8c845870e273861e7d60df49663/keystores | ||
kubectl create secret generic v3-operator-wallet-data --from-file=/home/username/.stakewise/0xeefffd4c23d2e8c845870e273861e7d60df49663/wallet | ||
``` | ||
|
||
The command deploys v3-operator on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists various ways to override default configuration during deployment. | ||
|
||
> **Tip**: List all releases using `helm list` | ||
> Replace `0xeefffd4c23d2e8c845870e273861e7d60df49663` with the actual vault contract address | ||
## Uninstalling the Chart | ||
## Installing the Chart | ||
|
||
To uninstall/delete the `my-release` deployment: | ||
To install the chart with the release name `v3-operator`, execute the following commands: | ||
|
||
```bash | ||
$ helm delete my-release | ||
helm repo add stakewise https://charts.stakewise.io | ||
helm install v3-operator stakewise/v3-operator \ | ||
--set settings.network="goerli" \ | ||
--set settings.vault="0xeefffd4c23d2e8c845870e273861e7d60df49663" \ | ||
--set settings.executionEndpoints="https://node.example.com/execution" \ | ||
--set settings.consensusEndpoints="https://node.example.com/consensus" \ | ||
--set settings.depositDataSecretName: "v3-operator-deposit-data" \ | ||
--set settings.keystoresSecretName: " v3-operator-keystores-data" \ | ||
--set settings.walletSecretName: "v3-operator-wallet-data" | ||
``` | ||
|
||
The command removes all the Kubernetes components associated with the chart and deletes the release. | ||
This command deploys the v3-operator with default configuration. Refer to the configuration section to learn more about customizing your deployment. | ||
|
||
## Configuration | ||
|
||
See `values.yaml` for configuration notes. Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, | ||
Alternatively, use a YAML file with specific values: | ||
|
||
```bash | ||
$ helm install my-release stakewise/v3-operator --set settings.network="XXXXXXXX" --set settings.executionEndpoint="XXXXXXXX" --set settings.consensusEndpoint="XXXXXXXX" --set settings.keystoresPassword="XXXXXXXX" --set settings.depositData="XXXXXXXX" --set settings.operatorPrivateKey="XXXXXXXX" | ||
$ helm install v3-operator stakewise/v3-operator -f values.yaml | ||
``` | ||
|
||
The above command specifies the web3 endpoint. | ||
> **Tip**: You can override the default [values.yaml](values.yaml) | ||
> **Tip**: List all releases using `helm list` | ||
## Uninstalling the Chart | ||
|
||
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example, | ||
To uninstall/delete the `v3-operator` deployment, use: | ||
|
||
```bash | ||
$ helm install my-release stakewise/v3-operator -f values.yaml | ||
$ helm delete v3-operator | ||
``` | ||
|
||
> **Tip**: You can override the default [values.yaml](values.yaml) | ||
This command removes all Kubernetes components associated with the chart and deletes the release. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters