Hi all, For those who failed their first attempt (54%) like me, don't be dishea . . .

Kubernetes
#1

Anand:
Hi all,

For those who failed their first attempt (54%) like me, don’t be disheartened; just take it as another opportunity to hone your skills.

TBH, i was a bit dejected on constantly seeing people post messages about passing the exam and that I couldn’t. Took me a few days to realise life is not about positives. Hence thought of writing message for those who dint pass in their first attempt and to let those people know you are not alone in this

Pros:

  1. Knew what to expect from proctor
  2. To restart terminal in case it gets stuck
  3. What kind of questions i can expect
  4. Time management
  5. And most importantly you would get an email stating the areas you need to improve (which really helped me)
    Cons:
  6. Only 1 attempt left

Passed in 2nd attempt with 78% :slightly_smiling_face:

“It’s not about how hard you hit. It’s about how hard you can get hit and keep moving forward”

#2

Zack:
Good and great you got yourself together. Crack the rest … congratulations and good luck

#3

Ravi Singh:
Hey Anand, Congratulations! Would you please elaborate on first point?

#4

I failed yesterday, want to know how did you solve the problem of setting container port from the evironment variable. I am getting an error:
Pod.spec.containers[0].ports[0].containerPort): invalid type for io.k8s.api.core.v1.ContainerPort.containerPort: got “string”, expected “integer”

Could not answer in exam.

#5

Hello, @shankumajumdar
It’s happening because of double quotes.
simple text - with double quotes it assumes it as string and without it assumes it as integer.

user-324
user-3241325×773 33.9 KB

#6

Thanks…but i need to use envrionment variable over there. e.g. define env variable port with value=80 and try to assign there.

#7

So you were asked to set an env variable where key:value would be port=80?

There are two ways to do this, depending on what you were using…first is the easiest way:

apiVersion: v1
kind: Pod
metadata:
  name: envar-demo
spec:
  containers:
  - name: envar-demo-container
    image: gcr.io/google-samples/node-hello:1.0
    env:
    - name: port
      value: "80"

But if you are using a pod that is a webserver and they want you to have an env variable that displays what the actual configured port is?

I have no idea how you would get to that info since none of the env.valueFrom options can dig into Pod.spec.containers[].ports[].ContainerPort.

I wish I could be of more help here but without knowing exactly what you are asking, I can’t better answer you.