Open stan-dot opened 5 months ago
Whatever decisions and learning come out of this are going to be applicable to the other beamline repositories
note: this tool is more suited to aws and isn't that well-developed https://chaostoolkit.org/reference/tutorials/containerising/
potential alternatives
raised a chaos-mesh ticket with the cloud team about the namespace creation
moved to looking into a more restricted tool - https://github.com/asobti/kube-monkey
working on it
tracking the cloud aspect here https://jira.diamond.ac.uk/servicedesk/customer/portal/2/SCHD-6072
might use litmus https://github.com/litmuschaos/litmus
Workflow Controller: The Argo Workflow Controller responsible for the creation of Chaos Experiments using the Chaos Experiment CR.
and argo isn't quite ready yet? might need to delay this https://docs.litmuschaos.io/docs/architecture/chaos-execution-plane
this is not on the critical path, deprioritizing
explore cluster resilience testing
options considered: