You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -160,13 +160,12 @@ In order for your custom applications and deployments to work, make sure they ha
160
160
161
161
- Deployments and pods must contain label `app=<name>`. This label is used forselecting targetsin a target namespace. Label key can be changed via environment variables (see [Scheduler's README](https://github.com/iskorotkov/chaos-scheduler)).
162
162
- Pods should contain a single container. Now it's only possible to induce failures on the first container in the pod, so all additional containers will be ignored.
163
-
- Deployments and pods must be annotated with `litmuschaos.io/chaos: "true"`. This annotation prevents Litmus from invoking more damage on your application than expected. See [Litmus docs](https://docs.litmuschaos.io/docs/getstarted/).
164
163
165
164
## FAQ and troubleshooting
166
165
167
166
Q: All failures don't work.
168
167
169
-
A: Check [requirements](#requirements). All target deployments and pods must have the matching label `app=<name>` and annotation `litmuschaos.io/chaos: "true"`.
168
+
A: Check [requirements](#requirements). All target deployments and pods must have the matching label `app=<name>`.
0 commit comments