on 20-Jun-2019 (Thu)

Question

In kubernetes, if you have a container running in a pod called 'test-deployment-abcd", issue command to get access to all the logs the container app is sending to stdout:

Answer

kubectl logs test-deployment-abcd

^^ note for "kubectl logs", "kubectl exec", "kubectl run" commands you don't need to follow up with resource type "pod", just follow up with pod name (or new deployment name in case of "kubectl run")

Question

In kubernetes, if you have a set of pods (each with a container running the same app), you can group them together for the purpose of internal, or more importantly, external exposure via a kubernetes concept called [...]

Answer

service

^^ note that service is created behind the scenes via issueing the "kubectl expose" command.

Question

In kubernetes, scaling (up or down) an app is accomplished by changing the number of [...] s in a Deployment. Hint: answer is not "pod", as that is too obvious.

Answer

replicas

Question

In kubernetes, when you scale up your deployment to use multiple pods, load-balancing is automatically handled by the kubernetes [...] used to expose the deployment (to external traffic).

Answer

service

Question

In kubernetes, if you do a rolling update (via "kubectl set image" command) and things go bad (i.e. one or more pods are no longer available), you can rollback via the "kubectl [...] [...] " command

Answer

kubectl rollout undo

^^ you can either rollback to immediate previous version, e.g.: kubectl rollout undo deployment kubernetes-bootcamp

^^^ or you can rollback to a specific previous version number, e.g.: kubectl rollout undo deployment kubernetes-bootcamp --to-revision=2

^^^^ to get the previuos versions/revision of a deployment, you can do "kubectl rollout history deployment kubernetes-bootcamp"