Feature Requests

I need to restrict users with project or org admin roles from creating, running, or deleting anything on Chaos, such as Chaos Infra, Experiments, and Chaos Hub. It would be beneficial if OPA policy support could be extended beyond Pipeline to include these entities, allowing for more granular control over user permissions.

Emails are expected to be encrypted. Please provide the feature to encrypt it.

Please provide the steps to uninstall looker

MongoDB queries to extract the experiment count/details at project Level for given date range as we are planning to uninstall looker dashboard

What is Required from harness Have a text field while creating a experiment so that the team can input their Hypothesis. Once the experiment is created have another text field (max up to 300 words), so that the team can input their Observation, risks, mitigation plan etc. After 1 and 2, these fields should be present in the reports so that the team can download Harness reports that has the context on hypothesis, observations, risks etc.

This request is regarding the new fault type: JVM: Stress Heap/Stack Mem.

We need Recovery as a vital section to execute even in the case of chaos abortion. We encountered an issue in process kill that after the process was killed the continuous probe failed and experiment was aborted due to this and could not start the processes. So, we request you to enable the Recovery as an essential section which should execute in abortion condition also.

We need support for expression-type matching to target multiple processes in Linux Native Agent.

I want to create my own fault/experiment and want to know how the operator knows about the fault. For example, "pod-delete" is a known fault for the litmus operator, but if I want to add my own fault named "terminate-pod", how can I do that? Where does that logic go and how does the operator know about "terminate-pod"? Some of the items Specific database faults(Mongodb,cassandra,graphdb etc) Application level faults(not just spring-boot) Stopping specific Azure service instead of Instance MQ/ESB level faults

Incorporate the manual changes we had to do on the delegate file which was used for SMTP Setup