Installing Cloud Service Mesh on Google Kubernetes Engine avis

Logesh kumar M. · Examiné il y a 16 jours

Lex C. · Examiné il y a 17 jours

ATISH G. · Examiné il y a 17 jours

Aruna T. · Examiné il y a 19 jours

Hiren G. · Examiné il y a 20 jours

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. · Examiné il y a 20 jours

Bolian Y. · Examiné il y a 20 jours

C_49_Ayush_Rawarkar G. · Examiné il y a 20 jours

Peter B. · Examiné il y a 20 jours

jeremy c. · Examiné il y a 20 jours

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. · Examiné il y a 20 jours

Gauri L. · Examiné il y a 20 jours

Yuichi T. · Examiné il y a 21 jours

Yuichi T. · Examiné il y a 21 jours

Stephen A. · Examiné il y a 21 jours

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

Paul H. · Examiné il y a 21 jours

megha u. · Examiné il y a 21 jours

Aman K. · Examiné il y a 21 jours

Stephen A. · Examiné il y a 22 jours

Karen S. · Examiné il y a 22 jours

Raja S. · Examiné il y a 22 jours

Porchelvi S. · Examiné il y a 22 jours

vakkalanka d. · Examiné il y a 22 jours

the GKE cluster creation takes more than 30 mins and fails

Anush G. · Examiné il y a 23 jours

Asif R. · Examiné il y a 23 jours