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: README.md
+18-1
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,17 @@ In Validator Lab we can deploy and test new validator features quickly and easil
9
9
10
10
## How to run
11
11
12
+
### Requirements
13
+
1) Docker. Create `docker` group add user to `docker` group
14
+
```
15
+
sudo usermod -aG docker $USER
16
+
newgrp docker
17
+
```
18
+
2) jq
19
+
```
20
+
sudo apt install jq
21
+
```
22
+
12
23
### Setup
13
24
Ensure you have the proper permissions to connect to the Monogon Kubernetes endpoint. Reach out to Leo on slack if you need the key (you do if you haven't asked him in the past).
- By default, validator stakes are baked into genesis on genesis creation. That way when the cluster boots up, all validators will consistently be in the leader schedule.
123
+
- If you do not want this and instead want the stake to warm up after deplyoyment, pass in the flag `--skip-primordial-stakes`.
For steps (2) and (3), when using `--no-bootstrap`, we assume that the directory at `--cluster-data-path <directory>` has the correct genesis, bootstrap identity, and faucet account stored. These are all created in step (1).
157
172
158
-
Note: We can't deploy heterogeneous clusters across v1.17 and v1.18 due to feature differences. Hope to fix this in the future. Have something where we can specifically define which features to enable.
173
+
Notes:
174
+
1) We can't deploy heterogeneous clusters across v1.17 and v1.18 due to feature differences. Hope to fix this in the future. Have something where we can specifically define which features to enable.
175
+
2) Heterogenous clusters with primordial stakes baked into genesis is not supported yet
159
176
160
177
## Querying the RPC from outside the cluster
161
178
The cluster now has an external IP/port that can be queried to reach the cluster RPC. The external RPC port will be logged during cluster boot, e.g.:
0 commit comments