Opinie (AHYBRID041 Observing Anthos Services)

Ismael U. · Sprawdzono ponad rok temu

This lab needs a fix and some basic proofreading. It is annoying that you provide such low-quality content. 1. loadgenerator doesn't start. This breaks the lab beginning with Task 6. ``` $ kubectl get deployments/loadgenerator NAME READY UP-TO-DATE AVAILABLE AGE loadgenerator 0/1 1 0 15m ``` ``` $ kubectl logs deployments/loadgenerator Error from server (BadRequest): container "main" in pod "loadgenerator-66c47bdc74-7j2mg" is waiting to start: PodInitializing ``` ``` $ kubectl describe pod/loadgenerator-66c47bdc74-7j2mg Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 16m default-scheduler Successfully assigned default/loadgenerator-66c47bdc74-7j2mg to gke-gke-pool-12345-5d62d571-7883 Normal Pulling 16m kubelet Pulling image "gcr.io/gke-release/asm/proxyv2:1.18.7-asm.4" Normal Pulled 16m kubelet Successfully pulled image "gcr.io/gke-release/asm/proxyv2:1.18.7-asm.4" in 6.36s (6.36s including waiting) Normal Created 16m kubelet Created container istio-validation Normal Started 16m kubelet Started container istio-validation Normal Pulled 16m kubelet Successfully pulled image "busybox:latest" in 983ms (983ms including waiting) Normal Pulled 14m kubelet Successfully pulled image "busybox:latest" in 329ms (329ms including waiting) Normal Pulled 11m kubelet Successfully pulled image "busybox:latest" in 162ms (162ms including waiting) Normal Pulling 9m25s (x4 over 16m) kubelet Pulling image "busybox:latest" Normal Pulled 9m25s kubelet Successfully pulled image "busybox:latest" in 165ms (165ms including waiting) Normal Created 9m24s (x4 over 16m) kubelet Created container frontend-check Normal Started 9m24s (x4 over 16m) kubelet Started container frontend-check Warning BackOff 62s (x15 over 12m) kubelet Back-off restarting failed container frontend-check in pod loadgenerator-66c47bdc74-7j2mg_default(ffb5ce3e-d24a-4461-98c8-2dbd770bd424) ``` 2. `kubectl get configmap` should be `kubectl get configmap -n istio-system` The respective `Output:` section below should be updated accordingly as well. Probably smth like: `kubectl get configmap istio-asm-managed -n istio-system -o yaml`. 3. The instruction "Return to the Workloads and Services & Ingress pages..." doesn't make sense, as there's no instruction to go there preceding it. 4. The instruction "to do one of the following" in #6 of the "Install the Online Boutique application on the GKE cluster" makes no sense, as the only activity proposed is "Look on the Services & Ingress page within the console." 5. Lastly,  in "Set Latency Threshold to 1000" unit is missing. 1000 what?

Maciej S. · Sprawdzono ponad rok temu

sasank k. · Sprawdzono ponad rok temu

Aleksandra G. · Sprawdzono ponad rok temu

Denys F. · Sprawdzono ponad rok temu

Emmanuel S. · Sprawdzono ponad rok temu

Jose E. · Sprawdzono ponad rok temu

Ross S. · Sprawdzono ponad rok temu

Charuhas K. · Sprawdzono ponad rok temu

Sasa P. · Sprawdzono ponad rok temu

Sarita R. · Sprawdzono ponad rok temu

Shubhachandra H. · Sprawdzono ponad rok temu

Abhay C. · Sprawdzono ponad rok temu

Rafael L. · Sprawdzono ponad rok temu

Horrible! Instructions very hard to follow, no match between descriptions and cloud screens. No counter available to check the progress!

Marius A. · Sprawdzono ponad rok temu

Harshitha B. · Sprawdzono ponad rok temu

Mukesh R. · Sprawdzono ponad rok temu

Leonardo C. · Sprawdzono ponad rok temu

Paul T. · Sprawdzono ponad rok temu

Beatriz Adriana O. · Sprawdzono ponad rok temu

Farhanuddin M. · Sprawdzono ponad rok temu

Stefano M. · Sprawdzono ponad rok temu

Harshal B. · Sprawdzono ponad rok temu