Installing Cloud Service Mesh on Google Kubernetes Engine Reviews

Logesh kumar M. · Reviewed 16 days ago

Lex C. · Reviewed 17 days ago

ATISH G. · Reviewed 17 days ago

Aruna T. · Reviewed 19 days ago

Hiren G. · Reviewed 20 days ago

1. Executive Summary During Task 5 of Lab GSP654, the execution of the asmcli script fails to complete successfully. The script times out after 600 seconds while waiting for the canonical-service-controller-manager deployment to become available. Investigation reveals that the underlying issue is a container image pull failure (ImagePullBackOff) for the deployment's sidecar proxy container, preventing the pods from reaching a Ready state. 2. Problem Statement The execution of the asmcli tool fails to successfully apply controller.yaml due to an ImagePullBackOff error. The deployment is unable to pull the container image gcr.io/kubebuilder/kube-rbac-proxy:v0.13.1 (or alternative external references like bitnami/kube-rbac-proxy), causing the kubectl wait command to reach its 600-second progress deadline and time out. The underlying cause is the inability of the private GKE node pool to resolve or reach the public external registries for this specific image, combined with missing image tags in the upstream repository, preventing the sidecar container from reaching a Ready state.

Stephen A. · Reviewed 20 days ago

Bolian Y. · Reviewed 20 days ago

C_49_Ayush_Rawarkar G. · Reviewed 20 days ago

Peter B. · Reviewed 20 days ago

jeremy c. · Reviewed 20 days ago

Issue: Deployment failure in Lab GSP654 ("Installing Cloud Service Mesh on Google Kubernetes Engine") during Task 5. Problem Statement: The execution of asmcli fails to apply controller.yaml due to an ImagePullBackOff error. The deployment is unable to pull the container image gcr.io/kubebuilder/kube-rbac-proxy:v0.13.1, causing the kubectl wait command to reach its progress deadline and time out. The underlying cause is the inability of the private GKE node pool to resolve or reach the public gcr.io registry for this specific image, preventing the sidecar container from reaching a Ready state.

Stephen A. · Reviewed 20 days ago

Gauri L. · Reviewed 20 days ago

Yuichi T. · Reviewed 21 days ago

Yuichi T. · Reviewed 21 days ago

Stephen A. · Reviewed 21 days ago

In some steps the asmcli: has looped Waiting for deployment... but in fact it was good

Paul H. · Reviewed 21 days ago

megha u. · Reviewed 21 days ago

Aman K. · Reviewed 21 days ago

Stephen A. · Reviewed 22 days ago

Karen S. · Reviewed 22 days ago

Raja S. · Reviewed 22 days ago

Porchelvi S. · Reviewed 22 days ago

vakkalanka d. · Reviewed 22 days ago

the GKE cluster creation takes more than 30 mins and fails

Anush G. · Reviewed 23 days ago

Asif R. · Reviewed 23 days ago