Initial Chaos-Mesh integration
As a step towards https://github.com/celestiaorg/knuu/issues/287, we can start by not integrating chaos-mesh in knuu programmatically, but instead install it in the Robusta cluster and expose its dashboard.
Then, whoever is running a workload on Robusta that has a ton of validators and want to play with the validators, they can just use the dashboard and target validators with the different kind of failures.
If we find this useful, then we can start integrating little by little the fault types we want to run in our tests so that we have test suites with the different failure types we interested in.
Note: installing chaos-mesh in the cluster is all about adding a few workloads to the cluster. Check here Note 2: In order to avoid accidentally playing with others' tests, we can ask devs to run the workloads in a separate namespace if they want to use chaos-mesh on them.
We just deployed chaos-mesh to Robusta.
URL: https://chaos-mesh.celestia-robusta.com/
Token: 1Password -> Shared -> chaos-mesh token
When you run a simulation with knuu, please copy the scope as shown in the logs of knuu. Use the scope name as a namespace selector when creating chaos to avoid interfering with other tests and simulations.
please copy the scope as shown in the logs of knuu.
What do you mean by copy the scope?
please copy the scope as shown in the logs of knuu.
What do you mean by copy the scope?
When running a simulation or test with knuu, you will see something like:
time="2024-05-08T11:53:11+02:00" level=info msg="LOG_LEVEL: info" file="knuu/knuu.go:175"
time="2024-05-08T11:53:11+02:00" level=info msg="Initializing knuu with scope: 20240508-115311-361" file="knuu/knuu.go:80"
In this case, the scope is 20240508-115311-361, which you must use as the namespace selector.
Aaah, I see. Thanks
done