Managing Deployments Using Kubernetes EngineGo to Lab
lab suggestion - strongly recommend students WAIT and CONFIRM functionality between the create deployment and create services commands. I was able to get my first try on this lab into a broken state where ngnix would not start. kubectl create -f deployments/frontend.yaml kubectl create -f services/frontend.yaml I used this command to easily see what was up and confirm all was ready before the next command: kubectl get deployments;kubectl get replicasets;kubectl get pods;kubectl get services Sample Output: AME READY UP-TO-DATE AVAILABLE AGE auth 1/1 1 1 4m26s frontend 1/1 1 1 34s hello 3/3 3 3 2m57s NAME DESIRED CURRENT READY AGE auth-65c65db967 1 1 1 4m27s frontend-569465456f 1 1 1 35s hello-6f984c9f74 3 3 3 2m58s NAME READY STATUS RESTARTS AGE auth-65c65db967-x85dt 1/1 Running 0 4m27s frontend-569465456f-7pkb5 1/1 Running 0 35s hello-6f984c9f74-8nfbq 1/1 Running 0 2m58s hello-6f984c9f74-drxpn 1/1 Running 0 2m58s hello-6f984c9f74-h6wq4 1/1 Running 0 2m58s NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE auth ClusterIP 10.51.246.180 <none> 80/TCP 3m35s frontend LoadBalancer 10.51.241.33 <pending> 443:32693/TCP 3s hello ClusterIP 10.51.244.71 <none> 80/TCP 106s kubernetes ClusterIP 10.51.240.1 <none> 443/TCP 6m1s
The lab did not registered my progress although I was getting the expected output.