Service Health
Incident affecting Google Kubernetes Engine
We are experiencing an issue with Google Kubernetes Engine.
Incident began at 2019-10-31 16:41 and ended at 2019-11-02 10:00 (all times are US/Pacific).
Date | Time | Description | |
---|---|---|---|
| 1 Nov 2019 | 12:42 PDT | Our engineers have determined that Google Kubernetes Engine (GKE) was impacted by the same underlying issue as the Google Compute Engine (GCE) incident. The start & end times have been updated in this incident to reflect the approximate impact period. Please refer to https://status.cloud.google.com/incident/compute/19008 for the full impact details of the incident. No further updates will be provided here. |
| 1 Nov 2019 | 08:53 PDT | The issue with creating new Google Kubernetes Engine clusters has been resolved for all affected projects as of Friday, 2019-11-01 08:50 US/Pacific. We thank you for your patience while we've worked on resolving the issue. |
| 1 Nov 2019 | 07:17 PDT | Description: Mitigation work is currently underway by our engineering team. We will provide more information by Friday, 2019-11-01 09:00 US/Pacific. Diagnosis: Cluster creation might fail with NetworkUnavailable status set to True. For existing clusters, new nodes might be created without network routes. As a result, autoscaler might not be able to add capacity to the cluster. Workaround: None at this time |
| 1 Nov 2019 | 05:52 PDT | Description: We are experiencing an issue with Google Kubernetes Engine beginning at Thursday, 2019-10-31 17:00 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2019-11-01 07:00 US/Pacific with current details. Diagnosis: Cluster creation might fail with NetworkUnavailable status set to True. For existing clusters, new nodes might be created without network routes. As a result, autoscaler might not be able to add capacity to the cluster. Workaround: None at this time |
| 1 Nov 2019 | 05:29 PDT | Description: We are experiencing an issue with Google Kubernetes Engine beginning at Thursday, 2019-10-31 17:00 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2019-11-01 06:00 US/Pacific with current details. Diagnosis: Cluster creation might fail with NetworkUnavailable status set to True. For existing clusters, adding a new node might fail. Autoscaler might not be able to increase the number of nodes. Workaround: None at this time |
- All times are US/Pacific