Guys, are Readiness and Liveness probes on CKA?

Kubernetes
#1

Bryan Tanoue:
Guys, are Readiness and Liveness probes on CKA?

#2

Fernando Jimenez:
Nope.

#3

Bryan Tanoue:
Thank You. I found this question on someones site:

#4

Bryan Tanoue:

Create a pod box0 with image busybox and command sleep 30; touch /tmp/debug; sleep 30; rm /tmp/debug. The pod should not be ready until the file /tmp/debug is available in the pod. If the file doesn't exist, the pod must restart.
#5

Bryan Tanoue:
I didn’t really learn about liveness probes in the class, but knew about them from OpenShift.

#6

Fernando Jimenez:
At this time, readiness and liveness probes are the domain of the CKAD, but not the CKA.

#7

Bryan Tanoue:
Thanks Fernando!

#8

Bryan Tanoue:
I have one more question.

#9

Bryan Tanoue:

kubectl create deployment deploy01 --image=nginx --record=true
#10

Bryan Tanoue:
I keep getting:

#11

Bryan Tanoue:

Error: unknown flag: --record
#12

Bryan Tanoue:
But the help file says --record is an option. Any ideas?

#13

Fernando Jimenez:
Yeah. The --record flag only works for objects that you have already created and you are editing. It will place the whole command in an annotation in the object. But kubectl create deploy doesn’t make sense since you are creating it and not modifying it.

#14

Bryan Tanoue:

Ahh.  OK, this makes sense.  So say I did
#15

Fernando Jimenez:
You can use it as kubectl edit deploy <deploy-name> --record

#16

Bryan Tanoue:
kubectl set image deployment/deploy01 nginx=nginx:dev --record

#17

Fernando Jimenez:
Exactly!

#18

Bryan Tanoue:
Since the deployment is there, it will then annotate. Now it makes way more sense. I was wondering why the revision 1 was blank and trying to figure out a way to capture my imperative command.

#19

Fernando Jimenez:
The set image is editing in place the image and with --record you’ll see your command given in the annotation.

#20

Bryan Tanoue:
It’s nice to know that kubectl edit works as well, since I’ve done that as a short cut.