Add: Litmus Chaos and Chaos Mess for chaos engineering

[nlamirault]

Signed-off-by: Nicolas Lamirault [email protected]

[mingrammer]

I think these tools are for k8s. Right?

[nlamirault]

Yes @mingrammer
i was hesitant to put chaos in kubernetes actually.

[mingrammer]

Hm, which do you think is better for these among onprem.chaos, k8s.ecosystem, or new cloudnative.chaos?

[nlamirault]

@mingrammer cloudnative.chaos 👍

[wolfspyre]

I don't really know what I'm talking about here, so take my input well salted; but I personally think chaos might fit better as a primary resource with the specific tools within the space contained within it. Alternatively, it might fit better as a branch off of generic IE: generic.chaos.obnoxiousPRCommenter ;)

[mingrammer]

@wolfspyre But these tools are for k8s and cloud-native applications. So I think cloudnative.chaos or k8s.ecosystem might be better for these.

[mingrammer]

Please re-run the autogen to add cloudnative provider.

[nlamirault]

@mingrammer done.

[mingrammer]

@nlamirault Ah, since the cloudnative is a new provider, you need to do some extra work to support a new provider.

You should add the cloudnative to config.py, and add the some functions for cloudnative to resource.py.

Sorry for that there is no guideline for adding a new provider, I'll add a guideline for this.

[mingrammer]

@nlamirault Wait .. hmm we need to re-discuss about which provider is suitable for these tools. Jaeger is also cloud native projet, but it could be under the onprem provider, so I think cloudnative provider could be getting a little vague. wdyt?

[nlamirault]

@mingrammer LitmusChaos and ChaosMesh are for Kubernetes. So, why not k8s.chaos like k8s.ecosystem is for Kubernetes tools.

[mingrammer]

@nlamirault k8s.chaos sounds good to me.

[nlamirault]

@mingrammer Done.

[mingrammer]

LGTM!