Add instructions in litmus-docs to run litmus on Okteto

litmuschaos / litmus

Litmus helps SREs and developers practice chaos engineering in a Cloud-native way. Chaos experiments are published at the ChaosHub (https://hub.litmuschaos.io). Community notes is at https://hackmd.io/a4Zu_sH4TZGeih-xCimi3Q

https://litmuschaos.io

Apache License 2.0

4.43k stars 693 forks source link

Add instructions in litmus-docs to run litmus on Okteto #1800

Closed ksatchit closed 7 months ago

ksatchit commented 4 years ago

Okteto is focused on giving users a development environment right on the cluster, with the Okteto Cloud providing namespaces for getting started w/ in-cluster development and simulate dev/ci/prod environments, with options to deploy pre-configured application templates.

This issue will track the creation of the resources/docs to run litmus on okteto in namespace scope, with the chaos experiments pulled as helm charts.

ksatchit commented 4 years ago

TODO

ns-scoped operator (openAPI schema validation needs to be updated as per latest changes!): https://github.com/litmuschaos/litmus/blob/master/docs/litmus-operator-namespaced-scope.yaml
helm charts for chaos experiments (needs update as per 1.6.1 & removal of helper images. Now we only need litmuschaos/go-runner): https://github.com/litmuschaos/litmus-helm/tree/master/charts/kubernetes-chaos

ksatchit commented 4 years ago

The namespaced operator manifest & associated docs are available with 1.6.2 images. Please refer to this doc for install & run instructions: https://docs.litmuschaos.io/docs/next/namespaced-mode/
The chaos CRs have been updated with latest image tags & schema enhancements in both sources: helm as well as chaoshub

Note: The changes may take a bit of time to reflect on the hub!

rberrelleza commented 4 years ago

This is an initial attempt from our side, leveraging the "develop on okteto" button to spin up litmus, an experiment, and the target application: https://github.com/okteto/litmus-on-okteto. Our goal is to make this into a tutorial or blog post for future reference.