关于“Installing Cloud Service Mesh on Google Kubernetes Engine”的评价
5719 条评价
Logesh kumar M. · 已于 16 days前审核
Lex C. · 已于 17 days前审核
ATISH G. · 已于 17 days前审核
Aruna T. · 已于 19 days前审核
Hiren G. · 已于 20 days前审核
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. · 已于 20 days前审核
Bolian Y. · 已于 20 days前审核
C_49_Ayush_Rawarkar G. · 已于 20 days前审核
Peter B. · 已于 20 days前审核
jeremy c. · 已于 20 days前审核
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. · 已于 20 days前审核
Gauri L. · 已于 20 days前审核
Yuichi T. · 已于 21 days前审核
Yuichi T. · 已于 21 days前审核
Stephen A. · 已于 21 days前审核
In some steps the asmcli: has looped Waiting for deployment... but in fact it was good
Paul H. · 已于 21 days前审核
megha u. · 已于 21 days前审核
Aman K. · 已于 21 days前审核
Stephen A. · 已于 22 days前审核
Karen S. · 已于 22 days前审核
Raja S. · 已于 22 days前审核
Porchelvi S. · 已于 22 days前审核
vakkalanka d. · 已于 22 days前审核
the GKE cluster creation takes more than 30 mins and fails
Anush G. · 已于 23 days前审核
Asif R. · 已于 23 days前审核
我们无法确保发布的评价来自已购买或已使用产品的消费者。评价未经 Google 核实。