Google Distributed Cloud (GDC) Edge customers are experiencing issues with creating new Google Kubernetes Engine (GKE...

The issue with Google Distributed Cloud Edge has been resolved for all affected users as of Saturday, 2024-03-23 18:43 US/Pacific. We thank you for your patience while we worked on resolving the issue.

Summary: Google Distributed Cloud (GDC) Edge customers are experiencing issues with creating new Google Kubernetes Engine (GKE) clusters. Description: We are experiencing an issue with Google Distributed Cloud Edge beginning on Wednesday, 2024-03-20. Our engineering team has identified the fix for the issue and mitigation work is currently underway by our engineering team. We will provide an update by Monday, 2024-03-25 17:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Customers attempting to create a new GKE cluster in a GDC Edge Zone may encounter timeout or internal errors , leading to cluster creation failures. Existing clusters are not affected by the issue. Workaround: Affected customers can run the following command gcloud projects add-iam-policy-binding ${PROJ} --member serviceAccount:service-${PROJ}@gcp-sa-edgecontainercluster.iam.gserviceaccount.com --role roles/viewer Please substitute ${PROJ} with appropriate PROJECT_NUMBER

Summary: Google Distributed Cloud (GDC) Edge customers are experiencing issues with creating new Google Kubernetes Engine (GKE) clusters. Description: We are experiencing an issue with Google Distributed Cloud Edge beginning on Wednesday, 2024-03-20. Our engineering team has identified the fix for the issue and working on identifying effective fix roll out plan. We will provide an update by Thursday, 2024-03-21 16:30 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Customers attempting to create a new GKE cluster in a GDC Edge Zone may encounter timeout or internal errors , leading to cluster creation failures. Existing clusters are not affected by the issue. Workaround: Affected customers can run the following command gcloud projects add-iam-policy-binding ${PROJ} --member serviceAccount:service-${PROJ}@gcp-sa-edgecontainercluster.iam.gserviceaccount.com --role roles/viewer Please substitute ${PROJ} with appropriate PROJECT_NUMBER

Summary: Google Distributed Cloud (GDC) Edge customers are experiencing issues with creating new Google Kubernetes Engine (GKE) clusters. Description: We are experiencing an issue with Google Distributed Cloud Edge beginning on Wednesday, 2024-03-20. Our engineering team has identified the root cause and is working on a mitigation plan. We will provide an update by Thursday, 2024-03-21 14:30 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Customers attempting to create a new GKE cluster in a GDC Edge Zone may encounter timeout or internal errors , leading to cluster creation failures. Existing clusters are not affected by the issue. Workaround: Affected customers can run the following command gcloud projects add-iam-policy-binding ${PROJ} --member serviceAccount:service-${PROJ}@gcp-sa-edgecontainercluster.iam.gserviceaccount.com --role roles/viewer Please substitute ${PROJ} with appropriate PROJECT_NUMBER

Summary: Google Distributed Cloud (GDC) Edge customers are experiencing issues with creating new Google Kubernetes Engine (GKE) clusters. Description: We are experiencing an issue with Google Distributed Cloud Edge beginning on Wednesday, 2024-03-20. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2024-03-21 12:30 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Customers attempting to create a new GKE cluster in a GDC Edge Zone may encounter timeout or internal errors , leading to cluster creation failures. Existing clusters are not affected by the issue. Workaround: Affected customers can run the following command gcloud projects add-iam-policy-binding ${PROJ} --member serviceAccount:service-${PROJ}@gcp-sa-edgecontainercluster.iam.gserviceaccount.com --role roles/viewer Please substitute ${PROJ} with appropriate PROJECT_NUMBER