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
I'm not sure which image is being referred to, nor what is Chaos-Operator (it's not in the concept of Litmus 3.x?). The docs link also seems to link to non-existent doc page. Is there a more up-to-date procedure?
My goal is to create a custom chaos experiment, and run it in my local kind cluster for testing.
- (Optional) Once the experiment has been validated using the above step, it can also be tested against the standard Litmus chaos
flow. This involves:
- Creating a custom image built with the code validated by the previous steps
- Launching the Chaos-Operator
- Modifying the ChaosExperiment manifest (experiment.yaml) with right defaults (env & other attributes, as applicable) & creating
this CR on the cluster (pointing the `.spec.definition.image` to the custom one just built)
- Modifying the ChaosEngine manifest (engine.yaml) with right app details, run properties & creating this CR to launch the chaos pods
- Verifying the experiment status via ChaosResult
Refer [litmus docs](https://docs.litmuschaos.io/docs/getstarted/) for more details on performing each step in this procedure.
The text was updated successfully, but these errors were encountered:
I figured out how to build the go-runner image, using the Makefile in this repo. I suppose the next step is to commit the new charts and connect a new ChaosHub repo using the dashboard? However I'm still unsure of the folder structure of the charts, as it differs from this video quite a lot.
Hi, this part in the developer guide is unclear to me.
I'm not sure which image is being referred to, nor what is Chaos-Operator (it's not in the concept of Litmus 3.x?). The docs link also seems to link to non-existent doc page. Is there a more up-to-date procedure?
My goal is to create a custom chaos experiment, and run it in my local kind cluster for testing.
The text was updated successfully, but these errors were encountered: