Hi @Javier3 ,
Can you please share more context? what do you mean by “still is not ok”?
You are not getting a green tick mark on that given description after removing the shell and specifying the mentioned fields on the pod?
Regards,
KodeKloud Support
Yes, that’s it. The shells are not available in the pod. I can’t access, executing kubectl exec… and still I don’t have the green check. I can share with you what I did…
I don’t know if it’s checking the file /etc/passwd or if the ash & sh are not available, both… honestly I don’t know.
@Ayman I did it too
root@controlplane ~
k exec -it dev-webapp -n dev sh
kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] – [COMMAND] instead.
OCI runtime exec failed: exec failed: container_linux.go:367: starting container process caused: exec: “sh”: executable file not found in $PATH: unknown
command terminated with exit code 126
I don’t get a green klick althought i have prevent the exec to run with a startup probe:
kubectl exec --stdin --tty -n staging staging-webapp – ash
OCI runtime exec failed: exec failed: container_linux.go:367: starting container process caused: exec: “ash”: executable file not found in $PATH: unknown
command terminated with exit code 126
Of course, it works before modifying the pod. After disabling the shells, you can not access.
Same here, I don’t know what they are checking.
Hi @Javier3 ,
Can you please DM me your manifest file? So you are having an issue only with this question?
Regards,
Hello, @Tej-Singh-Rana I can’t send it, I don’t know how. I can’t find the message button in your avatar.
EDIT: I’ve already sent it
Thanks for your help
I have removed all command in /bin of the pod. No exec commands work on it after that but still the check fails 
Now I able to solve 4 of the problems. 2 remain. Trying to create network policy fails. I have labelled the ns and created netpol based on namespace selector.
No, I can’t… I’ve sent the yaml to the admins, but I never got his answer
If the question requires only ingress to be allowed from prod namespace and egress is allowed from pods to outside prod namespace then the wordings of the question is wrong. Scratch… scratch 
Is there a bounty 
Clicking on the sa arrow should throw some details. Seems this part of the diagram is not working properly, assumed from the arrow what is expected and voila got a congratulations … 
