AHYBRID041 Anthos サービスのモニタリング のレビュー

Cherkashin Valeriy · 約2年前にレビュー済み

The entire lab seems half broken. The SLO is full of permission errors, some interfaces don't have anything that matches the descriptions written, the asmcli command hanged twice, traces were not being exported, the demo app was slow at all times (not just after the canary deployment), etc. Overall, the entire thing needs to be revisited.

Borsoi Ross Angelo · 約2年前にレビュー済み

mohanty subhasis · 約2年前にレビュー済み

Mishra Abhaya · 約2年前にレビュー済み

good one

kumar sumit · 約2年前にレビュー済み

Jainabadkar Ritesh · 約2年前にレビュー済み

Springwala Abbasali · 約2年前にレビュー済み

Springwala Abbasali · 約2年前にレビュー済み

Jadhav Manoj · 約2年前にレビュー済み

Ull Ismael · 約2年前にレビュー済み

Ull Ismael · 約2年前にレビュー済み

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?

Sieczka Maciej · 約2年前にレビュー済み

karusala sasank · 約2年前にレビュー済み

Gromak Aleksandra · 約2年前にレビュー済み

Frolov Denys · 約2年前にレビュー済み

Schilling Emmanuel · 約2年前にレビュー済み

Escobar Jose · 約2年前にレビュー済み

Stevenson Ross · 約2年前にレビュー済み

Khadse Charuhas · 約2年前にレビュー済み

Popovic Sasa · 約2年前にレビュー済み

Raghuwanshi Sarita · 約2年前にレビュー済み

Hotpeti Shubhachandra · 約2年前にレビュー済み

Chopade Abhay · 約2年前にレビュー済み

Luvisari Rafael · 約2年前にレビュー済み

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

Alexandru Marius · 約2年前にレビュー済み