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

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.

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.

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.

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.

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.