Unable to set up Chaos testing

[yuvaraj-shanmugam-at-optum-com]

What happened: Unable to bring up few PODs

NAME READY STATUS RESTARTS AGE chaos-litmus-auth-server-6898f756d5-zfxdd 0/1 Init:CreateContainerConfigError 0 17m chaos-litmus-frontend-7687ccc6cd-2cgxv 1/1 Running 0 17m chaos-litmus-mongo-0 0/1 CreateContainerConfigError 0 17m chaos-litmus-server-5848b4494b-flbrg 0/1 Init:CreateContainerConfigError 0 17m

K8s events:

C:\Users\syuvaraj>kubectl get events -n litmus | findstr /s "Failed" 17m Warning Failed pod/chaos-litmus-auth-server-6898f756d5-zfxdd Error: container has runAsNonRoot and image has non-numeric user (curl_user), cannot verify user is non-root (pod: "chaos-litmus-auth-server-6898f756d5-zfxdd_litmus(0202cebb-e113-45f8-ad75-3d58f577f952)", container: wait-for-mongodb) 16m Warning Failed pod/chaos-litmus-mongo-0 Error: container has runAsNonRoot and image will run as root (pod: "chaos-litmus-mongo-0_litmus(10647772-f6cf-4bde-a5d3-f29b17938b11)", container: mongo) 17m Warning Failed pod/chaos-litmus-server-5848b4494b-flbrg Error: container has runAsNonRoot and image has non-numeric user (curl_user), cannot verify user is non-root (pod: "chaos-litmus-server-5848b4494b-flbrg_litmus(6e3b7398-e831-4f11-98a2-8e878539e2e4)", container: wait-for-mongodb)

What you expected to happen: Expecting chaos-litmus-server, frontend server and auth-server PODs should be in ready state

Where can this issue be corrected? (optional)

How to reproduce it (as minimally and precisely as possible): We are using AWS EKS service.

Anything else we need to know?: We followed below documentation - https://aws.amazon.com/blogs/containers/chaos-engineering-with-litmuschaos-on-amazon-eks/

[prithvi1307]

Hi @yuvaraj-shanmugam-at-optum-com Can you join the Slack community and ask the same question? To join the slack, please follow the following steps: Step 1: Join the Kubernetes slack using the following link: https://slack.k8s.io/ Step 2: Join the #litmus channel on the Kubernetes slack or use this link after joining the Kubernetes slack: https://slack.litmuschaos.io/

[avaakash]

Hi, @yuvaraj-shanmugam-at-optum-com was this issue resolved? If yes, can you comment on your approach?

[avaakash]

Closing this issue due to inactivity, if the problem is still not resolved, feel free to re-open this.