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:
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")
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:
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:
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")
| status | not learned | measured difficulty | 37% [default] | last interval [days] | |||
|---|---|---|---|---|---|---|---|
| repetition number in this series | 0 | memorised on | scheduled repetition | ||||
| scheduled repetition interval | last repetition or drill |