🎯 Problem to be solved
We may want to run charon performance tests as a dv-pod transitions from dkg to runtime for the first time.
🛠️ Proposed solution
The first time we're transitioning to charon run for the first time (or another sensible way of making it once only, we don't want it running every restart/update imo), we run a charon alpha test infra --flags --publish.
Ideally this command is run with the correct enr in the k8s secret, (instead of auto generating a key in the test command) and then we could match the performance report to the exact node in a cluster.
🧪 Tests
👐 Additional acceptance criteria
❌ Out of Scope
Nice to have idea after this: We could do SQL querys on the back end between lockfile enrs and performance data enrs, and maybe show the test results to the appropriate operator address on their dashboard.
🎯 Problem to be solved
We may want to run charon performance tests as a dv-pod transitions from dkg to runtime for the first time.
🛠️ Proposed solution
The first time we're transitioning to
charon runfor the first time (or another sensible way of making it once only, we don't want it running every restart/update imo), we run acharon alpha test infra --flags --publish.Ideally this command is run with the correct enr in the k8s secret, (instead of auto generating a key in the test command) and then we could match the performance report to the exact node in a cluster.
🧪 Tests
👐 Additional acceptance criteria
❌ Out of Scope
Nice to have idea after this: We could do SQL querys on the back end between lockfile enrs and performance data enrs, and maybe show the test results to the appropriate operator address on their dashboard.