Console

Service Health

This page provides status information on the services that are part of Google Cloud. Check back here to view the current status of the services listed below. If you are experiencing an issue not listed here, please contact Support. Learn more about what's posted on the dashboard in this FAQ. For additional information on these services, please visit https://cloud.google.com/.

Incident affecting Google Kubernetes Engine

Autopilot (clusters versions >= 1.23) may break some workloads

Incident began at 2022-11-08 12:01 and ended at 2022-11-08 19:31 (all times are US/Pacific).

Previously affected location(s)

Taiwan (asia-east1)Hong Kong (asia-east2)Tokyo (asia-northeast1)Osaka (asia-northeast2)Seoul (asia-northeast3)Mumbai (asia-south1)Delhi (asia-south2)Singapore (asia-southeast1)Jakarta (asia-southeast2)Sydney (australia-southeast1)Melbourne (australia-southeast2)Warsaw (europe-central2)Finland (europe-north1)Madrid (europe-southwest1)Belgium (europe-west1)London (europe-west2)Frankfurt (europe-west3)Netherlands (europe-west4)Zurich (europe-west6)Milan (europe-west8)Paris (europe-west9)Montréal (northamerica-northeast1)Toronto (northamerica-northeast2)São Paulo (southamerica-east1)Santiago (southamerica-west1)Iowa (us-central1)South Carolina (us-east1)Northern Virginia (us-east4)Columbus (us-east5)Dallas (us-south1)Oregon (us-west1)Los Angeles (us-west2)Salt Lake City (us-west3)Las Vegas (us-west4)

Date Time Description
8 Nov 2022 19:31 PST

The issue with Google Kubernetes Engine has been resolved for all affected users as of Tuesday, 2022-11-08 19:27 US/Pacific.

We thank you for your patience while we worked on resolving the issue.
8 Nov 2022 17:14 PST

Summary: Autopilot (clusters versions >= 1.23) may break some workloads

Description: We are experiencing an issue with Google Kubernetes Engine.

Our engineering team continues to investigate the issue.

We will provide an update by Tuesday, 2022-11-08 19:30 US/Pacific with current details.

We apologize to all who are affected by the disruption.

Diagnosis: 1. Customers are unable to apply partner workloads (twistlock,Splunk Otel-Connector) 2. Customer may experience workloads admitted in 1.22, unable to create/schedule new pods as part of deployment after upgrading to 1.23+

Workaround: Action Required: Upgrades of Autopilot clusters to 1.23+ should be blocked to prevent more clusters from migrating from allowlistv1 to allowlistv2.
8 Nov 2022 16:01 PST

Summary: Autopilot (clusters versions >= 1.23) may break some workloads

Description: We are experiencing an issue with Google Kubernetes Engine.

Our engineering team continues to investigate the issue.

We will provide an update by Tuesday, 2022-11-08 17:30 US/Pacific with current details.

We apologize to all who are affected by the disruption.

Diagnosis: 1. Customers are unable to apply partner workloads (twistlock,Splunk Otel-Connector) 2. Customer may experience workloads admitted in 1.22, unable to create/schedule new pods as part of deployment after upgrading to 1.23+

Workaround: Action Required: Upgrades of Autopilot clusters to 1.23+ should be blocked to prevent more clusters from migrating from allowlistv1 to allowlistv2.
8 Nov 2022 13:17 PST

Summary: Autopilot (clusters versions >= 1.23) may break some workloads

Description: We are experiencing an issue with Google Kubernetes Engine.

Our engineering team continues to investigate the issue.

We will provide an update by Tuesday, 2022-11-08 15:30 US/Pacific with current details.

We apologize to all who are affected by the disruption.

Diagnosis: 1. Customers are unable to apply partner workloads (twistlock,Splunk Otel-Connector) 2. Customer may experience workloads admitted in 1.22, unable to create/schedule new pods as part of deployment after upgrading to 1.23+

Workaround: Action Required: Upgrades of Autopilot clusters to 1.23+ should be blocked to prevent more clusters from migrating from allowlistv1 to allowlistv2.
8 Nov 2022 13:17 PST

Summary: Autopilot (clusters versions >= 1.23) may break some workloads

Description: We are experiencing an issue with Google Kubernetes Engine.

Our engineering team continues to investigate the issue.

We will provide an update by Tuesday, 2022-11-08 13:30 US/Pacific with current details.

We apologize to all who are affected by the disruption.

Diagnosis: 1. Customers are unable to apply partner workloads (twistlock,Splunk Otel-Connector) 2. Customer may experience workloads admitted in 1.22, unable to create/schedule new pods as part of deployment after upgrading to 1.23+

Workaround: Action Required: Upgrades of Autopilot clusters to 1.23+ should be blocked to prevent more clusters from migrating from allowlistv1 to allowlistv2.