Pod container as ENV

Kubernetes
#1

Is it possible to define Pod container spec as ENV? one question that really threw me off is when I saw the pod with container with env.
I did not know how to add another side block because primary was under the env

#2

If I understand you right – and I might not – then you saw a container spec like this:

    containers:
    - env:
       - name: TEAM
          value: blue
       name: my-container
       image: my-image

That’s not unusual, and the keys in a container spec can appear in any order. In this case, env appears first. But so could name, image or any other valid spec key.

#3

that is correct. Now if I want to add the side car and copy name and image. do I have to indent name or the image whichever is the first with the prefix (-) or it is easier to create env for side car too by copying the entire block to avoid messing the indentation during the exam?

I think I got it now. Actually, container is not under the env. Infact the name and image is at the same level. Visually it almost it looked like it was under this during the exam. Should have paid the close attention and move the name block on top with “-” and created second container without the env

#4

Yeah; env, name and image are all at the same level; it’s not so clear in my snippet, but that’s the case.

#5

I got stuck on that question and network policy. Network policy I was trying to apply restriction to pod on the namespace and instead of adding podselector{} I ended up adding namespace: name which of course was not acceptable at the policy level.
Also, spend 15 mins twice for not changing context and did not get to finish update.
I was thinking I might fail again due to bad time management but I got through finally,

Thanks for all the prompt the responses and clarification.

This was most challenging exam compare to Microsoft, and other certs I have done in the fast. Now i will continue my journey with Linux admin, CKS and CKAD