Service Health
Incident affecting Google Kubernetes Engine
Node pool creation failing in multiple zones
Incident began at 2017-04-26 11:45 and ended at 2017-04-27 17:51 (all times are US/Pacific).
Date | Time | Description | |
---|---|---|---|
| 27 Apr 2017 | 18:02 PDT | The issue with GKE Node Pool creation has been resolved for all affected projects as of 17:51 US/Pacific. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence. |
| 27 Apr 2017 | 17:30 PDT | We have identified the problem on the backend and currently commencing a rollback. We'll provide more information by 18:00 PST. |
| 27 Apr 2017 | 17:02 PDT | We are investigating an issue with Google Container Engine (GKE) that is affecting node-pool creations in the following zones: asia-east1-a, asia-east1-c, asia-northeast1-a, asia-northeast1-b, asia-northeast1-c, asia-southeast1-a, asia-southeast1-b, europe-west1-b, europe-west1-c, us-central1-b, us-central1-f, us-east1-c, us-west1-a, us-west1-b and us-east1-d. We will provide more information by 17:30 US/Pacific. |
- All times are US/Pacific