Access First Cluster Lab Guide

[Mybarry]

Using Branch PKS 1.4 Step 3.3 fails. When I run the command:
kubectl run busybox --rm --image=busybox -it --restart=Never -- sh
I never bet the command prompt. It just hangs and I have to Ctl-C after some time.

Not sure what else to do. Has this particular cli been verified?

[afewellvmware]

Interesting @Mybarry , I havent gone through that lab guide myself, I find the -rm flag troubling, does it work if you try it without -rm?

[afewellvmware]

OK I looked at the lab guide and have a more clear picture, I dont see anything obviously wrong with the syntax of the command, not sure why its hanging like that. If you could open a seperate putty session to cli-vm and use it to kubectl describe the pod and maybe look at logs, it may give some better insight. I have to run to an appointment now but will try to replicate this later. Thanks!

[Mybarry]

Found the issue: the nginx-test pod is never actually deployed! From the log:
ubuntu@cli-vm:$ kubectl get pods
NAME READY STATUS RESTARTS AGE
nginx-test 0/1 ImagePullBackOff 0 3h57m
ubuntu@cli-vm:$ kubectl logs nginx-test
Error from server (BadRequest): container "nginx-test" in pod "nginx-test" is waiting to start: trying and failing to pull image

Do you know WHERE it is pulling this image from?

[Mybarry]

Maybe a OneCloud resource/issue? I tried another lab guide and all my pods are stuck in STATUS: ContainerCreating,ImagePullBackOff..................................

[afewellvmware]

Issue appears to be caused as k8s cluster was not enabled for outbound internet access, it was installed per instructions in LAG-MC1322, will leave issue open until lab guide updated