Prerequisites
This section describes the requirements, such as chaos infrastructure and project-level permissions required to execute chaos experiments on your target environments.
Requirements for individual chaos faults
In the chaos faults reference, you'll find fault-specific requirements listed in the Use cases section of each fault, as shown, for example, in the use cases for the Kubelet service kill fault.
Chaos infrastructure requirements
The table below lists the chaos infrastructure execution plane components and the required resources. You can install these components in your target cluster, allowing the chaos infrastructure to run experiments here. Chaos infrastructure runs within your target environment to aid CE in accessing the target resources and injecting chaos at a cloud-native scale.
Deployment | Container | CPU required | Memory required | Image |
---|---|---|---|---|
chaos-operator-ce | chaos-operator-ce | 125m | 300M | chaosnative/chaos-operator |
chaos-exporter | chaos-exporter | 125m | 300M | chaosnative/chaos-exporter |
subscriber | subscriber | 125m | 300M | chaosnative/harness-chaos-subscriber |
workflow-controller | workflow-controller | 125m | 300M | chaosnative/workflow-controller |
Add users to a project to run chaos experiments
You must have at least one user in a project, and set up permissions such that the user can perform chaos experiments. The following steps generate an email invitation to the new user(s) to add themselves to the project.
To add a new user to a project:
-
In Harness, select a project.
-
Expand the Project setup menu, and select Access Control.
This page lists all the users added to the current project.
-
Select New User, and then:
- In New User(s), add the email(s) of the user(s) you want to add.
- In User Groups, select any of the existing user groups to which you can add the user.
- Add the roles for the user(s) to enforce their access permissions.
-
Select Apply.