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
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.
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
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 …
@Anudeep-Nalla it is simple. Just follow the document and read the yaml syntax example properly and replicate. Read question for dev and staging one of the questions is more descriptive.