feat: aztec-network helm chart #8078
Conversation
| @@ -0,0 +1,57 @@ | |||
| apiVersion: apps/v1 | |||
| kind: Deployment | |||
There was a problem hiding this comment.
should this be stateful? If this is just for short running tests i guess not?
There was a problem hiding this comment.
Yeah it probably should/will. We might be able to test L1 censorship by killing the anvil pod, and when it comes back it shouldn't start from scratch.
just-mitch
force-pushed
the
mt/7999-basic-helm-chart
branch
from
a62f452 to
9e60d71
Compare
just-mitch
force-pushed
the
mt/7999-basic-helm-chart
branch
from
d66d497 to
56d5922
Compare
| [ | ||
| "/bin/sh", | ||
| "-c", | ||
| "cp /scripts/deploy-contracts.sh /tmp/deploy-contracts.sh && chmod +x /tmp/deploy-contracts.sh && /tmp/deploy-contracts.sh", |
There was a problem hiding this comment.
Is this a new script, I can't see it. But would it be better to use the deploy-l1-contracts command on aztec?
nvm, seen the inline script further down.
| - name: ETHEREUM_HOST | ||
| value: {{ include "aztec-network.ethereumHost" . | quote }} | ||
| - name: P2P_ENABLED | ||
| value: "{{ .Values.bootNode.p2p.enabled }}" |
There was a problem hiding this comment.
Won't this be overridden by the cli option?
There was a problem hiding this comment.
Yep, good catch.
| [ | ||
| "/bin/bash", | ||
| "-c", | ||
| "source /shared/contracts.env && env && node --no-warnings /usr/src/yarn-project/aztec/dest/bin/index.js start --node p2pEnabled=true --archiver --sequencer --prover --pxe", |
There was a problem hiding this comment.
Did you mean to start a pxe? And I don't think running a --prover as part of the node does anything now.
There was a problem hiding this comment.
Nice. I took both out.
Edit: Actually, having a pxe on the bootnode is useful for other nodes who want to use the get-node-info cli command.
| - name: VALIDATOR_PRIVATE_KEY | ||
| value: "0x47e179ec197488593b187f80a00eb0da91f1b9d0b13f8733639f19c30a34926a" | ||
| ports: | ||
| - containerPort: 8080 |
There was a problem hiding this comment.
Shoud these be the values in the ENV VARS?
| command: | ||
| - "/bin/bash" | ||
| - "-c" | ||
| - "source /shared/contracts.env && env && node --no-warnings /usr/src/yarn-project/aztec/dest/bin/index.js start --node --archiver --sequencer --prover" |
There was a problem hiding this comment.
Probably remove the --prover.
just-mitch
force-pushed
the
mt/7999-basic-helm-chart
branch
2 times, most recently
from
06b2a5c to
49bdebd
Compare
just-mitch
force-pushed
the
mt/7999-basic-helm-chart
branch
from
49bdebd to
bc53f9d
Compare
just-mitch
force-pushed
the
mt/7999-basic-helm-chart
branch
from
bc53f9d to
dd88e3d
Compare
Changes to circuit sizes
🧾 Summary (100% most significant diffs)
Full diff report 👇
|
Benchmark resultsMetrics with a significant change:
Detailed resultsAll benchmarks are run on txs on the This benchmark source data is available in JSON format on S3 here. Proof generationEach column represents the number of threads used in proof generation.
L2 block published to L1Each column represents the number of txs on an L2 block published to L1.
L2 chain processingEach column represents the number of blocks on the L2 chain where each block has 8 txs.
Circuits statsStats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.
Stats on running time collected for app circuits
AVM SimulationTime to simulate various public functions in the AVM.
Public DB AccessTime to access various public DBs.
Tree insertion statsThe duration to insert a fixed batch of leaves into each tree type.
MiscellaneousTransaction sizes based on how many contract classes are registered in the tx.
Transaction size based on fee payment method | Metric | | |
Initial definition of the helm chart for an "aztec-network".
Currently not part of CI (that is #8000).
However, a meaningful smoke test is included that can be run with: