Update GKE Cluster from version 1.25 to 1.26

[ke4]

Copy from the email from Google:

<blockquote type="cite" style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div><div id="forwardbody1" style="caret-color: rgb(0, 0, 0); font-family: Verdana, Geneva, sans-serif; font-size: 13.333333px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="background: rgb(250, 250, 250); font-family: Arial; font-weight: normal; margin: 0px; padding: 0px; width: 853px;">

Hello Google Kubernetes Engine (GKE) Customer,We're writing to let you know that the automatic upgrades from Kubernetes v1.25 to v1.26 will start on or after May 25, 2023. For this reason, we recommend updating all your clusters to use GA API before v1.25 reaches End of Life on February 29, 2024, to ensure continued API functionality.What do you need to know?Kubernetes project's lifecycle states that once the APIs graduate to general availability, previous alpha and beta APIs are eventually removed. Once beta APIs have been removed from Kubernetes v1.26, you can expect to experience some of the following behaviors:If GKE detects usage of the removed beta APIs in your clusters before upgrading to Kubernetes v1.26, Google will pause automatic minor upgrades until Kubernetes v1.25 reaches EoL for GKE clusters on that version. The minor upgrade pause is intended to let you perform a timely and nondisruptive transition from beta APIs removed in Kubernetes v1.26 to their newer supported versions.API clients won't be able to use the removed beta APIs in v1.26.Manifests using the removed beta APIs removed in Kubernetes v1.26 can no longer be applied.Previously persisted objects will remain functional and can be viewed and updated using the new API versions before and after upgrading to Kubernetes v1.26.What can you expect after Kubernetes v1.25 reaches EoL?We will automatically upgrade your clusters remaining on Kubernetes v1.25 to Kubernetes v1.26. Optionally, you can configure maintenance windows and exclusions to control scope and timing of automatic upgrades or to temporarily pause them. Cluster control planes are upgraded regularly.Please be advised that once Kubernetes v1.25 reaches EoL and Google upgrades your clusters to Kubernetes v1.26, you will no longer be able to access the removed beta API versions. Any remaining dependencies on these APIs may stop working.The GKE release schedule outlines the cluster upgrade schedule for Kubernetes v1.26. Please note the automatic upgrade start dates for the release channels and for clusters on a static version.What do you need to do?We recommend updating your software to use supported GA API versions. Updating your software before upgrading your clusters to Kubernetes v1.26 will ensure your API clients and resource manifests can continue to access and update API resources without disruption.Note: To assess the use of the removed APIs in your clusters, you can use Admin Activity log query with Google Cloud's operations suite enabled, to show the Kubernetes v1.26 APIs in use.Your projects below use the beta APIs removed in v1.26 and will require you to migrate to the newer API versions before your clusters are upgraded to v1.26:pdbe-test-312214pdbe-af-prod-317014prj-ext-prod-dtol-gcp-drprj-ext-prod-faang-gcp-drprj-ext-prod-reactomegsa-drpdbe-af-staging-317014golden-tenure-196110prj-int-dev-atlas-app-intgprj-ext-prod-asg-gcp-dr-349815We're here to helpIf you wish to learn more about how Kubernetes works, we suggest reading:How cluster upgrades workHow Kubernetes deprecations work with GKEDeprecated API migration guide for KubernetesThanks for choosing Google Kubernetes Engine. | Hello Google Kubernetes Engine (GKE) Customer,We're writing to let you know that the automatic upgrades from Kubernetes v1.25 to v1.26 will start on or after May 25, 2023. For this reason, we recommend updating all your clusters to use GA API before v1.25 reaches End of Life on February 29, 2024, to ensure continued API functionality.What do you need to know?Kubernetes project's lifecycle states that once the APIs graduate to general availability, previous alpha and beta APIs are eventually removed. Once beta APIs have been removed from Kubernetes v1.26, you can expect to experience some of the following behaviors:If GKE detects usage of the removed beta APIs in your clusters before upgrading to Kubernetes v1.26, Google will pause automatic minor upgrades until Kubernetes v1.25 reaches EoL for GKE clusters on that version. The minor upgrade pause is intended to let you perform a timely and nondisruptive transition from beta APIs removed in Kubernetes v1.26 to their newer supported versions.API clients won't be able to use the removed beta APIs in v1.26.Manifests using the removed beta APIs removed in Kubernetes v1.26 can no longer be applied.Previously persisted objects will remain functional and can be viewed and updated using the new API versions before and after upgrading to Kubernetes v1.26.What can you expect after Kubernetes v1.25 reaches EoL?We will automatically upgrade your clusters remaining on Kubernetes v1.25 to Kubernetes v1.26. Optionally, you can configure maintenance windows and exclusions to control scope and timing of automatic upgrades or to temporarily pause them. Cluster control planes are upgraded regularly.Please be advised that once Kubernetes v1.25 reaches EoL and Google upgrades your clusters to Kubernetes v1.26, you will no longer be able to access the removed beta API versions. Any remaining dependencies on these APIs may stop working.The GKE release schedule outlines the cluster upgrade schedule for Kubernetes v1.26. Please note the automatic upgrade start dates for the release channels and for clusters on a static version.What do you need to do?We recommend updating your software to use supported GA API versions. Updating your software before upgrading your clusters to Kubernetes v1.26 will ensure your API clients and resource manifests can continue to access and update API resources without disruption.Note: To assess the use of the removed APIs in your clusters, you can use Admin Activity log query with Google Cloud's operations suite enabled, to show the Kubernetes v1.26 APIs in use.Your projects below use the beta APIs removed in v1.26 and will require you to migrate to the newer API versions before your clusters are upgraded to v1.26:pdbe-test-312214pdbe-af-prod-317014prj-ext-prod-dtol-gcp-drprj-ext-prod-faang-gcp-drprj-ext-prod-reactomegsa-drpdbe-af-staging-317014golden-tenure-196110prj-int-dev-atlas-app-intgprj-ext-prod-asg-gcp-dr-349815We're here to helpIf you wish to learn more about how Kubernetes works, we suggest reading:How cluster upgrades workHow Kubernetes deprecations work with GKEDeprecated API migration guide for KubernetesThanks for choosing Google Kubernetes Engine. | Hello Google Kubernetes Engine (GKE) Customer,We're writing to let you know that the automatic upgrades from Kubernetes v1.25 to v1.26 will start on or after May 25, 2023. For this reason, we recommend updating all your clusters to use GA API before v1.25 reaches End of Life on February 29, 2024, to ensure continued API functionality.What do you need to know?Kubernetes project's lifecycle states that once the APIs graduate to general availability, previous alpha and beta APIs are eventually removed. Once beta APIs have been removed from Kubernetes v1.26, you can expect to experience some of the following behaviors:If GKE detects usage of the removed beta APIs in your clusters before upgrading to Kubernetes v1.26, Google will pause automatic minor upgrades until Kubernetes v1.25 reaches EoL for GKE clusters on that version. The minor upgrade pause is intended to let you perform a timely and nondisruptive transition from beta APIs removed in Kubernetes v1.26 to their newer supported versions.API clients won't be able to use the removed beta APIs in v1.26.Manifests using the removed beta APIs removed in Kubernetes v1.26 can no longer be applied.Previously persisted objects will remain functional and can be viewed and updated using the new API versions before and after upgrading to Kubernetes v1.26.What can you expect after Kubernetes v1.25 reaches EoL?We will automatically upgrade your clusters remaining on Kubernetes v1.25 to Kubernetes v1.26. Optionally, you can configure maintenance windows and exclusions to control scope and timing of automatic upgrades or to temporarily pause them. Cluster control planes are upgraded regularly.Please be advised that once Kubernetes v1.25 reaches EoL and Google upgrades your clusters to Kubernetes v1.26, you will no longer be able to access the removed beta API versions. Any remaining dependencies on these APIs may stop working.The GKE release schedule outlines the cluster upgrade schedule for Kubernetes v1.26. Please note the automatic upgrade start dates for the release channels and for clusters on a static version.What do you need to do?We recommend updating your software to use supported GA API versions. Updating your software before upgrading your clusters to Kubernetes v1.26 will ensure your API clients and resource manifests can continue to access and update API resources without disruption.Note: To assess the use of the removed APIs in your clusters, you can use Admin Activity log query with Google Cloud's operations suite enabled, to show the Kubernetes v1.26 APIs in use.Your projects below use the beta APIs removed in v1.26 and will require you to migrate to the newer API versions before your clusters are upgraded to v1.26:pdbe-test-312214pdbe-af-prod-317014prj-ext-prod-dtol-gcp-drprj-ext-prod-faang-gcp-drprj-ext-prod-reactomegsa-drpdbe-af-staging-317014golden-tenure-196110prj-int-dev-atlas-app-intgprj-ext-prod-asg-gcp-dr-349815We're here to helpIf you wish to learn more about how Kubernetes works, we suggest reading:How cluster upgrades workHow Kubernetes deprecations work with GKEDeprecated API migration guide for KubernetesThanks for choosing Google Kubernetes Engine. | Hello Google Kubernetes Engine (GKE) Customer,We're writing to let you know that the automatic upgrades from Kubernetes v1.25 to v1.26 will start on or after May 25, 2023. For this reason, we recommend updating all your clusters to use GA API before v1.25 reaches End of Life on February 29, 2024, to ensure continued API functionality.What do you need to know?Kubernetes project's lifecycle states that once the APIs graduate to general availability, previous alpha and beta APIs are eventually removed. Once beta APIs have been removed from Kubernetes v1.26, you can expect to experience some of the following behaviors:If GKE detects usage of the removed beta APIs in your clusters before upgrading to Kubernetes v1.26, Google will pause automatic minor upgrades until Kubernetes v1.25 reaches EoL for GKE clusters on that version. The minor upgrade pause is intended to let you perform a timely and nondisruptive transition from beta APIs removed in Kubernetes v1.26 to their newer supported versions.API clients won't be able to use the removed beta APIs in v1.26.Manifests using the removed beta APIs removed in Kubernetes v1.26 can no longer be applied.Previously persisted objects will remain functional and can be viewed and updated using the new API versions before and after upgrading to Kubernetes v1.26.What can you expect after Kubernetes v1.25 reaches EoL?We will automatically upgrade your clusters remaining on Kubernetes v1.25 to Kubernetes v1.26. Optionally, you can configure maintenance windows and exclusions to control scope and timing of automatic upgrades or to temporarily pause them. Cluster control planes are upgraded regularly.Please be advised that once Kubernetes v1.25 reaches EoL and Google upgrades your clusters to Kubernetes v1.26, you will no longer be able to access the removed beta API versions. Any remaining dependencies on these APIs may stop working.The GKE release schedule outlines the cluster upgrade schedule for Kubernetes v1.26. Please note the automatic upgrade start dates for the release channels and for clusters on a static version.What do you need to do?We recommend updating your software to use supported GA API versions. Updating your software before upgrading your clusters to Kubernetes v1.26 will ensure your API clients and resource manifests can continue to access and update API resources without disruption.Note: To assess the use of the removed APIs in your clusters, you can use Admin Activity log query with Google Cloud's operations suite enabled, to show the Kubernetes v1.26 APIs in use.Your projects below use the beta APIs removed in v1.26 and will require you to migrate to the newer API versions before your clusters are upgraded to v1.26:pdbe-test-312214pdbe-af-prod-317014prj-ext-prod-dtol-gcp-drprj-ext-prod-faang-gcp-drprj-ext-prod-reactomegsa-drpdbe-af-staging-317014golden-tenure-196110prj-int-dev-atlas-app-intgprj-ext-prod-asg-gcp-dr-349815We're here to helpIf you wish to learn more about how Kubernetes works, we suggest reading:How cluster upgrades workHow Kubernetes deprecations work with GKEDeprecated API migration guide for KubernetesThanks for choosing Google Kubernetes Engine.
-- | -- | -- | --
Hello Google Kubernetes Engine (GKE) Customer,We're writing to let you know that the automatic upgrades from Kubernetes v1.25 to v1.26 will start on or after May 25, 2023. For this reason, we recommend updating all your clusters to use GA API before v1.25 reaches End of Life on February 29, 2024, to ensure continued API functionality.What do you need to know?Kubernetes project's lifecycle states that once the APIs graduate to general availability, previous alpha and beta APIs are eventually removed. Once beta APIs have been removed from Kubernetes v1.26, you can expect to experience some of the following behaviors:If GKE detects usage of the removed beta APIs in your clusters before upgrading to Kubernetes v1.26, Google will pause automatic minor upgrades until Kubernetes v1.25 reaches EoL for GKE clusters on that version. The minor upgrade pause is intended to let you perform a timely and nondisruptive transition from beta APIs removed in Kubernetes v1.26 to their newer supported versions.API clients won't be able to use the removed beta APIs in v1.26.Manifests using the removed beta APIs removed in Kubernetes v1.26 can no longer be applied.Previously persisted objects will remain functional and can be viewed and updated using the new API versions before and after upgrading to Kubernetes v1.26.What can you expect after Kubernetes v1.25 reaches EoL?We will automatically upgrade your clusters remaining on Kubernetes v1.25 to Kubernetes v1.26. Optionally, you can configure maintenance windows and exclusions to control scope and timing of automatic upgrades or to temporarily pause them. Cluster control planes are upgraded regularly.Please be advised that once Kubernetes v1.25 reaches EoL and Google upgrades your clusters to Kubernetes v1.26, you will no longer be able to access the removed beta API versions. Any remaining dependencies on these APIs may stop working.The GKE release schedule outlines the cluster upgrade schedule for Kubernetes v1.26. Please note the automatic upgrade start dates for the release channels and for clusters on a static version.What do you need to do?We recommend updating your software to use supported GA API versions. Updating your software before upgrading your clusters to Kubernetes v1.26 will ensure your API clients and resource manifests can continue to access and update API resources without disruption.Note: To assess the use of the removed APIs in your clusters, you can use Admin Activity log query with Google Cloud's operations suite enabled, to show the Kubernetes v1.26 APIs in use.Your projects below use the beta APIs removed in v1.26 and will require you to migrate to the newer API versions before your clusters are upgraded to v1.26:pdbe-test-312214pdbe-af-prod-317014prj-ext-prod-dtol-gcp-drprj-ext-prod-faang-gcp-drprj-ext-prod-reactomegsa-drpdbe-af-staging-317014golden-tenure-196110prj-int-dev-atlas-app-intgprj-ext-prod-asg-gcp-dr-349815We're here to helpIf you wish to learn more about how Kubernetes works, we suggest reading:How cluster upgrades workHow Kubernetes deprecations work with GKEDeprecated API migration guide for KubernetesThanks for choosing Google Kubernetes Engine. | Hello Google Kubernetes Engine (GKE) Customer,We're writing to let you know that the automatic upgrades from Kubernetes v1.25 to v1.26 will start on or after May 25, 2023. For this reason, we recommend updating all your clusters to use GA API before v1.25 reaches End of Life on February 29, 2024, to ensure continued API functionality.What do you need to know?Kubernetes project's lifecycle states that once the APIs graduate to general availability, previous alpha and beta APIs are eventually removed. Once beta APIs have been removed from Kubernetes v1.26, you can expect to experience some of the following behaviors:If GKE detects usage of the removed beta APIs in your clusters before upgrading to Kubernetes v1.26, Google will pause automatic minor upgrades until Kubernetes v1.25 reaches EoL for GKE clusters on that version. The minor upgrade pause is intended to let you perform a timely and nondisruptive transition from beta APIs removed in Kubernetes v1.26 to their newer supported versions.API clients won't be able to use the removed beta APIs in v1.26.Manifests using the removed beta APIs removed in Kubernetes v1.26 can no longer be applied.Previously persisted objects will remain functional and can be viewed and updated using the new API versions before and after upgrading to Kubernetes v1.26.What can you expect after Kubernetes v1.25 reaches EoL?We will automatically upgrade your clusters remaining on Kubernetes v1.25 to Kubernetes v1.26. Optionally, you can configure maintenance windows and exclusions to control scope and timing of automatic upgrades or to temporarily pause them. Cluster control planes are upgraded regularly.Please be advised that once Kubernetes v1.25 reaches EoL and Google upgrades your clusters to Kubernetes v1.26, you will no longer be able to access the removed beta API versions. Any remaining dependencies on these APIs may stop working.The GKE release schedule outlines the cluster upgrade schedule for Kubernetes v1.26. Please note the automatic upgrade start dates for the release channels and for clusters on a static version.What do you need to do?We recommend updating your software to use supported GA API versions. Updating your software before upgrading your clusters to Kubernetes v1.26 will ensure your API clients and resource manifests can continue to access and update API resources without disruption.Note: To assess the use of the removed APIs in your clusters, you can use Admin Activity log query with Google Cloud's operations suite enabled, to show the Kubernetes v1.26 APIs in use.Your projects below use the beta APIs removed in v1.26 and will require you to migrate to the newer API versions before your clusters are upgraded to v1.26:pdbe-test-312214pdbe-af-prod-317014prj-ext-prod-dtol-gcp-drprj-ext-prod-faang-gcp-drprj-ext-prod-reactomegsa-drpdbe-af-staging-317014golden-tenure-196110prj-int-dev-atlas-app-intgprj-ext-prod-asg-gcp-dr-349815We're here to helpIf you wish to learn more about how Kubernetes works, we suggest reading:How cluster upgrades workHow Kubernetes deprecations work with GKEDeprecated API migration guide for KubernetesThanks for choosing Google Kubernetes Engine. | Hello Google Kubernetes Engine (GKE) Customer,We're writing to let you know that the automatic upgrades from Kubernetes v1.25 to v1.26 will start on or after May 25, 2023. For this reason, we recommend updating all your clusters to use GA API before v1.25 reaches End of Life on February 29, 2024, to ensure continued API functionality.What do you need to know?Kubernetes project's lifecycle states that once the APIs graduate to general availability, previous alpha and beta APIs are eventually removed. Once beta APIs have been removed from Kubernetes v1.26, you can expect to experience some of the following behaviors:If GKE detects usage of the removed beta APIs in your clusters before upgrading to Kubernetes v1.26, Google will pause automatic minor upgrades until Kubernetes v1.25 reaches EoL for GKE clusters on that version. The minor upgrade pause is intended to let you perform a timely and nondisruptive transition from beta APIs removed in Kubernetes v1.26 to their newer supported versions.API clients won't be able to use the removed beta APIs in v1.26.Manifests using the removed beta APIs removed in Kubernetes v1.26 can no longer be applied.Previously persisted objects will remain functional and can be viewed and updated using the new API versions before and after upgrading to Kubernetes v1.26.What can you expect after Kubernetes v1.25 reaches EoL?We will automatically upgrade your clusters remaining on Kubernetes v1.25 to Kubernetes v1.26. Optionally, you can configure maintenance windows and exclusions to control scope and timing of automatic upgrades or to temporarily pause them. Cluster control planes are upgraded regularly.Please be advised that once Kubernetes v1.25 reaches EoL and Google upgrades your clusters to Kubernetes v1.26, you will no longer be able to access the removed beta API versions. Any remaining dependencies on these APIs may stop working.The GKE release schedule outlines the cluster upgrade schedule for Kubernetes v1.26. Please note the automatic upgrade start dates for the release channels and for clusters on a static version.What do you need to do?We recommend updating your software to use supported GA API versions. Updating your software before upgrading your clusters to Kubernetes v1.26 will ensure your API clients and resource manifests can continue to access and update API resources without disruption.Note: To assess the use of the removed APIs in your clusters, you can use Admin Activity log query with Google Cloud's operations suite enabled, to show the Kubernetes v1.26 APIs in use.Your projects below use the beta APIs removed in v1.26 and will require you to migrate to the newer API versions before your clusters are upgraded to v1.26:pdbe-test-312214pdbe-af-prod-317014prj-ext-prod-dtol-gcp-drprj-ext-prod-faang-gcp-drprj-ext-prod-reactomegsa-drpdbe-af-staging-317014golden-tenure-196110prj-int-dev-atlas-app-intgprj-ext-prod-asg-gcp-dr-349815We're here to helpIf you wish to learn more about how Kubernetes works, we suggest reading:How cluster upgrades workHow Kubernetes deprecations work with GKEDeprecated API migration guide for KubernetesThanks for choosing Google Kubernetes Engine.
Hello Google Kubernetes Engine (GKE) Customer,We're writing to let you know that the automatic upgrades from Kubernetes v1.25 to v1.26 will start on or after May 25, 2023. For this reason, we recommend updating all your clusters to use GA API before v1.25 reaches End of Life on February 29, 2024, to ensure continued API functionality.What do you need to know?Kubernetes project's lifecycle states that once the APIs graduate to general availability, previous alpha and beta APIs are eventually removed. Once beta APIs have been removed from Kubernetes v1.26, you can expect to experience some of the following behaviors:If GKE detects usage of the removed beta APIs in your clusters before upgrading to Kubernetes v1.26, Google will pause automatic minor upgrades until Kubernetes v1.25 reaches EoL for GKE clusters on that version. The minor upgrade pause is intended to let you perform a timely and nondisruptive transition from beta APIs removed in Kubernetes v1.26 to their newer supported versions.API clients won't be able to use the removed beta APIs in v1.26.Manifests using the removed beta APIs removed in Kubernetes v1.26 can no longer be applied.Previously persisted objects will remain functional and can be viewed and updated using the new API versions before and after upgrading to Kubernetes v1.26.What can you expect after Kubernetes v1.25 reaches EoL?We will automatically upgrade your clusters remaining on Kubernetes v1.25 to Kubernetes v1.26. Optionally, you can configure maintenance windows and exclusions to control scope and timing of automatic upgrades or to temporarily pause them. Cluster control planes are upgraded regularly.Please be advised that once Kubernetes v1.25 reaches EoL and Google upgrades your clusters to Kubernetes v1.26, you will no longer be able to access the removed beta API versions. Any remaining dependencies on these APIs may stop working.The GKE release schedule outlines the cluster upgrade schedule for Kubernetes v1.26. Please note the automatic upgrade start dates for the release channels and for clusters on a static version.What do you need to do?We recommend updating your software to use supported GA API versions. Updating your software before upgrading your clusters to Kubernetes v1.26 will ensure your API clients and resource manifests can continue to access and update API resources without disruption.Note: To assess the use of the removed APIs in your clusters, you can use Admin Activity log query with Google Cloud's operations suite enabled, to show the Kubernetes v1.26 APIs in use.Your projects below use the beta APIs removed in v1.26 and will require you to migrate to the newer API versions before your clusters are upgraded to v1.26:pdbe-test-312214pdbe-af-prod-317014prj-ext-prod-dtol-gcp-drprj-ext-prod-faang-gcp-drprj-ext-prod-reactomegsa-drpdbe-af-staging-317014golden-tenure-196110prj-int-dev-atlas-app-intgprj-ext-prod-asg-gcp-dr-349815We're here to helpIf you wish to learn more about how Kubernetes works, we suggest reading:How cluster upgrades workHow Kubernetes deprecations work with GKEDeprecated API migration guide for KubernetesThanks for choosing Google Kubernetes Engine. | Hello Google Kubernetes Engine (GKE) Customer,We're writing to let you know that the automatic upgrades from Kubernetes v1.25 to v1.26 will start on or after May 25, 2023. For this reason, we recommend updating all your clusters to use GA API before v1.25 reaches End of Life on February 29, 2024, to ensure continued API functionality.What do you need to know?Kubernetes project's lifecycle states that once the APIs graduate to general availability, previous alpha and beta APIs are eventually removed. Once beta APIs have been removed from Kubernetes v1.26, you can expect to experience some of the following behaviors:If GKE detects usage of the removed beta APIs in your clusters before upgrading to Kubernetes v1.26, Google will pause automatic minor upgrades until Kubernetes v1.25 reaches EoL for GKE clusters on that version. The minor upgrade pause is intended to let you perform a timely and nondisruptive transition from beta APIs removed in Kubernetes v1.26 to their newer supported versions.API clients won't be able to use the removed beta APIs in v1.26.Manifests using the removed beta APIs removed in Kubernetes v1.26 can no longer be applied.Previously persisted objects will remain functional and can be viewed and updated using the new API versions before and after upgrading to Kubernetes v1.26.What can you expect after Kubernetes v1.25 reaches EoL?We will automatically upgrade your clusters remaining on Kubernetes v1.25 to Kubernetes v1.26. Optionally, you can configure maintenance windows and exclusions to control scope and timing of automatic upgrades or to temporarily pause them. Cluster control planes are upgraded regularly.Please be advised that once Kubernetes v1.25 reaches EoL and Google upgrades your clusters to Kubernetes v1.26, you will no longer be able to access the removed beta API versions. Any remaining dependencies on these APIs may stop working.The GKE release schedule outlines the cluster upgrade schedule for Kubernetes v1.26. Please note the automatic upgrade start dates for the release channels and for clusters on a static version.What do you need to do?We recommend updating your software to use supported GA API versions. Updating your software before upgrading your clusters to Kubernetes v1.26 will ensure your API clients and resource manifests can continue to access and update API resources without disruption.Note: To assess the use of the removed APIs in your clusters, you can use Admin Activity log query with Google Cloud's operations suite enabled, to show the Kubernetes v1.26 APIs in use.Your projects below use the beta APIs removed in v1.26 and will require you to migrate to the newer API versions before your clusters are upgraded to v1.26:pdbe-test-312214pdbe-af-prod-317014prj-ext-prod-dtol-gcp-drprj-ext-prod-faang-gcp-drprj-ext-prod-reactomegsa-drpdbe-af-staging-317014golden-tenure-196110prj-int-dev-atlas-app-intgprj-ext-prod-asg-gcp-dr-349815We're here to helpIf you wish to learn more about how Kubernetes works, we suggest reading:How cluster upgrades workHow Kubernetes deprecations work with GKEDeprecated API migration guide for KubernetesThanks for choosing Google Kubernetes Engine.
Hello Google Kubernetes Engine (GKE) Customer,We're writing to let you know that the automatic upgrades from Kubernetes v1.25 to v1.26 will start on or after May 25, 2023. For this reason, we recommend updating all your clusters to use GA API before v1.25 reaches End of Life on February 29, 2024, to ensure continued API functionality.What do you need to know?Kubernetes project's lifecycle states that once the APIs graduate to general availability, previous alpha and beta APIs are eventually removed. Once beta APIs have been removed from Kubernetes v1.26, you can expect to experience some of the following behaviors:If GKE detects usage of the removed beta APIs in your clusters before upgrading to Kubernetes v1.26, Google will pause automatic minor upgrades until Kubernetes v1.25 reaches EoL for GKE clusters on that version. The minor upgrade pause is intended to let you perform a timely and nondisruptive transition from beta APIs removed in Kubernetes v1.26 to their newer supported versions.API clients won't be able to use the removed beta APIs in v1.26.Manifests using the removed beta APIs removed in Kubernetes v1.26 can no longer be applied.Previously persisted objects will remain functional and can be viewed and updated using the new API versions before and after upgrading to Kubernetes v1.26.What can you expect after Kubernetes v1.25 reaches EoL?We will automatically upgrade your clusters remaining on Kubernetes v1.25 to Kubernetes v1.26. Optionally, you can configure maintenance windows and exclusions to control scope and timing of automatic upgrades or to temporarily pause them. Cluster control planes are upgraded regularly.Please be advised that once Kubernetes v1.25 reaches EoL and Google upgrades your clusters to Kubernetes v1.26, you will no longer be able to access the removed beta API versions. Any remaining dependencies on these APIs may stop working.The GKE release schedule outlines the cluster upgrade schedule for Kubernetes v1.26. Please note the automatic upgrade start dates for the release channels and for clusters on a static version.What do you need to do?We recommend updating your software to use supported GA API versions. Updating your software before upgrading your clusters to Kubernetes v1.26 will ensure your API clients and resource manifests can continue to access and update API resources without disruption.Note: To assess the use of the removed APIs in your clusters, you can use Admin Activity log query with Google Cloud's operations suite enabled, to show the Kubernetes v1.26 APIs in use.Your projects below use the beta APIs removed in v1.26 and will require you to migrate to the newer API versions before your clusters are upgraded to v1.26:pdbe-test-312214pdbe-af-prod-317014prj-ext-prod-dtol-gcp-drprj-ext-prod-faang-gcp-drprj-ext-prod-reactomegsa-drpdbe-af-staging-317014golden-tenure-196110prj-int-dev-atlas-app-intgprj-ext-prod-asg-gcp-dr-349815We're here to helpIf you wish to learn more about how Kubernetes works, we suggest reading:How cluster upgrades workHow Kubernetes deprecations work with GKEDeprecated API migration guide for KubernetesThanks for choosing Google Kubernetes Engine.

</div></div></div></blockquote>Hello Google Kubernetes Engine (GKE) Customer,

We're writing to let you know that the automatic upgrades from Kubernetes v1.25 to v1.26 will start on or after May 25, 2023. For this reason, we recommend updating all your clusters to use GA API before v1.25 reaches End of Life on February 29, 2024, to ensure continued API functionality.

What do you need to know?

[Kubernetes project's lifecycle](https://notifications.google.com/g/p/ACUgQrFs7Da9qp4T6122FHuGK9V04_2jVDrDKOPDPDwuj1s_VWjhm0sCSmoqetdIhBEzqG9GIyWiJJH5l8AU2lrfEAqfmfzfBmycUOXHRZ1pzT3AtFBRTXVe1Q5F5utS0khl_ejhvZNZtA2D_0lmSURKhqnwGlhWrlJ44SRJHq8zeRmAiuIq-Z3xVPAbHBfrEK11eAal2BYf23z8EDM4ZVrvGEmrIiaRMAXcPtWPJNYRvw) states that once the APIs graduate to general availability, previous alpha and [beta APIs](https://notifications.google.com/g/p/ACUgQrFSV_4n1JiTBII_jaiE7w3XSVg9Sz_mOHR9gBzd_S88iKaV26omudxXh1wtES38qmBT8nHSziwPrPE5CG_Q6qXrc8FLngx-vSWnK1YqERfyRqAAEgwDiEbcB4E5DPhsYBKUrfI8fM6TCkyds-_-EGq6L3K1gOEQGfgK8CsxYdgvHdm4Nldb73BG-VZ43k_T3IvipJIVGVjfM5-LDGZkPFIhaJYComfzxXlK4iIiJhW_OaRxuOW7) are eventually removed. Once beta APIs have been [removed from Kubernetes v1.26](https://notifications.google.com/g/p/ACUgQrFoiu5RakMxlK_Crt8oTE8pK-l5m_E-gKqcn6G39oHgWLQLpdu77OZFhpnFFxKv8PpbOAsPJje-kPXIfZodH3Pw485yqgEtAFZQfGMhlVM87wcCd01s_60CpDL5IVYLLIkOYw7_NSQP1KlHMUhykUvewS8_sug5fVUG6XiVLogB6oz9yKCTjoj8aWapHTe-VB9Lk9U_LysacysRzJYEN7Z1PGXOBHA6HVLN3DjpEwpL8jnjcjo), you can expect to experience some of the following behaviors:

If GKE detects usage of the removed beta APIs in your clusters before upgrading to Kubernetes v1.26, Google will [pause automatic minor upgrades ](https://notifications.google.com/g/p/ACUgQrFouKXeiPE9ewF6yLtTh9h3yGa5gaBLFC23HxBwesmh128sjDp9uleH2x1Ni6J5UODHHi9YGX5HOBzn9xjWgQtf4XAGbzvY9sucBFYy24ZUZEn8z7MYTB85ASQaWq1gqwY9i-Ly-2IV-BTBe0GZcO82e9o6guKFviWtwG3sRzt2HC4Sdqpt_8h4lIJtPa_n0zejb8RES-2Wky6-RstdYfi0OiE1ksE7jSkN7B0CWnLiNjYGU-i_klOb_4qTUJg)until Kubernetes v1.25 reaches EoL for GKE clusters on that version. The minor upgrade pause is intended to let you perform a timely and nondisruptive transition from beta APIs removed in Kubernetes v1.26 to their newer supported versions.
API clients won't be able to use the removed beta APIs in v1.26.
[Manifests](https://notifications.google.com/g/p/ACUgQrFTPosLE8zS0hRJJZQrl_tKe1focxD8dx-qyen9UrFxqCe3fyNcl0sBLqUQTW9osxptJfjt-ghGOK_Ha--0cI15vfERWBOQLYBOXgXzIUleBCHIKV20uvX_riX3kLzgXGZ0WezrNhTnT5CPFrjO-CcQcg4caQL2IZV4RBN99fouHFJ5PpHXJGGAHFmSTItE0rU6miEf4Whn5Yq9aAFFMTH1dMZf_eZ-QLMV2bIelRhcSkQJFPNAMUpsA7CB) using the removed beta APIs removed in Kubernetes v1.26 can no longer be applied.
Previously persisted objects will remain functional and can be viewed and updated using the new API versions before and after upgrading to Kubernetes v1.26.
What can you expect after Kubernetes v1.25 reaches EoL?

We will automatically upgrade your clusters remaining on Kubernetes v1.25 to Kubernetes v1.26. Optionally, you can configure [maintenance windows and exclusions](https://notifications.google.com/g/p/ACUgQrG5qPcGmrNRktWqBLwUf4YdS5yMtlaMW3UcNOkUMEx2qpcEXYijd0eVnIgK1lMH8Gq9VfHtsipvmXOQTREeNmkUEAJLjk7Tis36-BA0G9mYK47CE5pK-pEd1CJChkx7WcHwsG6-9566gdYHS8Wjp6I7hA0dX6_HJpjLbLEJaUmsIIWKKIJP50l3SMrjsWHpEZBOyvD-Hg622Cl08EoTKAlEtdWoR9SGs31lOv0d7vFVr64fnMv2Vsy62hDw-D-TVMHY3KZaCfQZnD8n) to control scope and timing of automatic upgrades or to temporarily pause them. Cluster control planes are [upgraded regularly](https://notifications.google.com/g/p/ACUgQrG1ELZ6w4rHmhsa_B4mOBaEODb1JNeK78Ammso4BLOe_7ecM3jqC1xT-pQ4s4dxMOT4OMh4_hZ5NeJQT1lWKYNHeoMKUvhZ_uSs0W_qkdepzFPj0i104ZQ5GUoHXcUppgVtkDczM10mH8GCkgBUTFkAW07Og9lm0VvvI7LD88JiCz8v-Tm42Pj8DsvsD6nir3_b2whbiyp6l85Q3GvBfhT0svOW9IjaK7BQxVj8PCtaeLFlm3ioB14).

Please be advised that once Kubernetes v1.25 reaches [EoL](https://notifications.google.com/g/p/ACUgQrGrQkrorvlVx246_LX9fX0o5SzUsbdHUwlzHU6ZQEFG3SNAEUiuHxhOGhGDspk1kDo6qvb2FuR1B9d9oRv3xCg_OA2MpuWc13DOKZQQwXX9nDcVfVCp6KI2Lf6u6zgIccSxHDtFcCu-wMnlLrzi16dyIZumo8KMYs2jOB5R4rCcE-d5IQG1k5ukkn8WRcyTYvbaA5eYSw457MWieIlxgplDTpf_X_brIMQbLpO_pDoltJ0prbWv4hA-j0aJoHLbhxjw4ez_s_gnjZQ-7o0) and Google upgrades your clusters to Kubernetes v1.26, you will no longer be able to access the removed beta API versions. Any remaining dependencies on these APIs may stop working.

The GKE [release schedule](https://notifications.google.com/g/p/ACUgQrEiwRvVmhyBCxWud7CwNaMl6Qs2u5103R5b0VM988XjfCPyeijkjWITlmaH5_KVdVxkHrzdBAeOti0yIa89HpqOf10qXeb7Do7eB-CibgZ6sbdJSSfeoLa4Y7qAl2Xk0cjsElDZ23AhHTRCarFawms-cH4i5bcxkKJ4EWc0K83JlvT5w9dw-un64-oCHtruuNP_FRWMwCuobfrMsRsboobgh2uRahPs81HhkdpB3Bo) outlines the cluster upgrade schedule for Kubernetes v1.26. Please note the automatic upgrade start dates for the release channels and for clusters on a static version.

What do you need to do?

We recommend updating your software to use [supported](https://notifications.google.com/g/p/ACUgQrFoiu5RakMxlK_Crt8oTE8pK-l5m_E-gKqcn6G39oHgWLQLpdu77OZFhpnFFxKv8PpbOAsPJje-kPXIfZodH3Pw485yqgEtAFZQfGMhlVM87wcCd01s_60CpDL5IVYLLIkOYw7_NSQP1KlHMUhykUvewS8_sug5fVUG6XiVLogB6oz9yKCTjoj8aWapHTe-VB9Lk9U_LysacysRzJYEN7Z1PGXOBHA6HVLN3DjpEwpL8jnjcjo) GA API versions. Updating your software before upgrading your clusters to Kubernetes v1.26 will ensure your API clients and resource manifests can continue to access and update API resources without disruption.

Note: To assess the use of the removed APIs in your clusters, you can use [Admin Activity log query](https://notifications.google.com/g/p/ACUgQrFoiu5RakMxlK_Crt8oTE8pK-l5m_E-gKqcn6G39oHgWLQLpdu77OZFhpnFFxKv8PpbOAsPJje-kPXIfZodH3Pw485yqgEtAFZQfGMhlVM87wcCd01s_60CpDL5IVYLLIkOYw7_NSQP1KlHMUhykUvewS8_sug5fVUG6XiVLogB6oz9yKCTjoj8aWapHTe-VB9Lk9U_LysacysRzJYEN7Z1PGXOBHA6HVLN3DjpEwpL8jnjcjo) with Google Cloud's operations suite enabled, to show the Kubernetes v1.26 APIs in use.

Your projects below use the beta APIs removed in v1.26 and will require you to migrate to the newer API versions before your clusters are upgraded to v1.26:

[pdbe-test-312214](https://notifications.google.com/g/p/ACUgQrEhpLv-ij8IJBPwesgRK1p3GL6IAu401FNuYKs7zXOUTh8e2rkodlKBkPEPeqRnMbi1ZE6dOlojHxM1UNypRv7O_vDDpb-_RviC6L2O-tyny8vV6pB72NZyt_vbMBXgy8rQGymogbn6iEb3X4QaHsqJPNI64Mc_EfX7-V6aA73U-m6Mf9bH2StsOX2dml71pqHL24w9a5nHhKIvNRcOoZZoOZODbGOIZw)
[pdbe-af-prod-317014](https://notifications.google.com/g/p/ACUgQrHeYBdoKzss_G9it_UBae4e5my_-PS8xUwkaRNaiVNjmLtTogD8oYmjOzVk0_k-wXzkxH-jHanUQ8cbitHPUO6WW4fjHo25JVVJPKH4CEK6NX1KP6XOrPKOD-jeEFiKsX2qcL14FYir61CxUrRhsNdnmrDEJMDbxyX_T1aRxT-2wuOCb_FgdV9qb2pADUvIiw85hnzycE8cJSmpLzNiMID9xQNCsN_73q87yQ)
[prj-ext-prod-dtol-gcp-dr](https://notifications.google.com/g/p/ACUgQrFntONnA1WTXj8-jhxQYK1oxPuOGVvrFP_4J1XCKyaQDxj5H_A-ZXo39H643pDOgkFKuUUW0fdmcvczzJ4q5sQxEBaRNTP6n02edKRsAQTk3z12VfDsju5fg9jRLA9PHLAR1E7p7IIUz4ErLHCVU_Oc5asF6iUDsjQjArgzVL9zVhIFOZJPpLrkd7wLeylu9KZEjXj5HNRM_WB7frTNgx86tIiNJmvhkIoOZ8dyEt37)
[prj-ext-prod-faang-gcp-dr](https://notifications.google.com/g/p/ACUgQrGwuUGUhfRwVpLMB8shOGNIDp26CA69yKici7etx_IWuKETNCgbgZ3eDqxNsoIPT_s1FqBCDIPp8P7GdnsJ1rxoGbwseN00sHHa4cJWwF8Z8GuaQD-ipKU6_k--ipqtYt7Wl27T7wnfnsR2tNYot3Vx6T1DXSJGWzBVgeJVJAvt3VVMBMq0ZAwUzZqeRvWE-dud9GQmHTmKd1O2DY1Y-6SpLbU5w6Jk7tx4yxEE0YcHHA)
[prj-ext-prod-reactomegsa-dr](https://notifications.google.com/g/p/ACUgQrELFpLaAEZWhB6BVVnPZV0KJNJep-N7wqSRs2QKjM5oxly_Qi2JbdKrWR8czggtfOYpJxzZLmZIpVb8C01ffD3qcBlZ_Zq17hjDZxsDjh5K0Et_eqp6qPaJRmlZhl6KKGdaSBpGdQsRLbNZ3Wup38UBdVbYJnOal6R6dwIasJ70xa0d4treiKu02zLFjxU_wGn5X4k0hTURD-vkSPiYFExSdT4JLWwSKrP7OeNGDZZcTcXh)
[pdbe-af-staging-317014](https://notifications.google.com/g/p/ACUgQrEtT8i56R9t6RdXR9Q5_dGdnzCfKVZ5d9yXKBWtZZxTWUqIsaYou4fxlHIYMEhWRPjuvTdPhPFz8eaPrUsjbs7fAs7R3VUb5Nrm2PPTb-f-aqD4rVOc7qRLYOfF0sPsiRhGdBF3wOB4SY5IfVM5jDQ1ycWbwGp8XBYQoatds9pycjl4p-b9b36dAeqmZeUAJDj_Cd3_Av8DT19rKVozjp-4Gt7xVsDkjRtH78Q8sA)
[golden-tenure-196110](https://notifications.google.com/g/p/ACUgQrFEiMEMoowhJ20zb9Ipgw69UU6VMLezpphfivvkM6RpM_LMu_fq0RRxCkCkfIOi57tlWkDMOZqB6CyVwOFtUAX--D5inGE4z5VMd4jVzJCO4uq0NgyYkHHp5otfeJfbNcNAF6goq9Ojc-lB7MwI6724uS2seVW4ZBO6im-_mBJ8bJCWy90gSvGaQ9oxqLGGav2na4RYnRaaLNimrokwj_nVUQfK3AE1iGKag7s)
[prj-int-dev-atlas-app-intg](https://notifications.google.com/g/p/ACUgQrHqL1MmCeQUigxLRH-G_2P2XoJoVRn4rzQOReafrYmcvmFlnc1HCw2h8bWxIClumw_pr0qzXofnHkE2u9UfQaQIumdl6FYIXncMGX9bK03VaizEB7Z5imqBhrvEJN9tg6zn0na0pCHy1Zv8Qy_4MYGF0YfP6CN1WbNXj3LIYJs-R-nrVLuOaDAiX46FrazyGdLkLZoiEa-B7vrQSDU6eduT0MGbOaj1bxJv9UkeIoqwhW0)
[prj-ext-prod-asg-gcp-dr-349815](https://notifications.google.com/g/p/ACUgQrHK3d0GWEG6YKji4ijwXHEHW9Cxc7TFgEWzlA2CJq5atdeOEltRIbAo80vuFe15ZkAHaMfJATDQFt35lUPDheI9DEr_3rg5jC04QfBl7DcGu9XCT1lmgPvWsu0dr0FCwuYxaj1OZQY1XRIiOxPBgsVtPHvEAr-LmNTeS-PW9SWEAoacXvNXF5kIhGVPbqs7kaL6bcvMjAwJfOhFihYnQ_Vq7OFP1Tn7tKf57CGDgsRSXAT4lKfw)
We're here to help

If you wish to learn more about how Kubernetes works, we suggest reading:

[How cluster upgrades work](https://notifications.google.com/g/p/ACUgQrGxyOZEmhj3meh0F9IxLRaBqUNtWVO0JfZ4dtap7u6IwMBdaBvxe-ezUMiuLN4nubEDivSshVFDDTI1oCYwFLy53ZnaqYqNoh7bp-kLCUtqii7ljWz6kBHEPpdLiLCr3OZme2teJiQc2kJSjgESyUTF-gWiJfjE2TtOO75WFpPdCnNTCZ-IoYDT0GSbXzwKOBeGMWhBFnWDUwKYDiiATlbhtOe5KXwfwxxXv_W4bcKaGjhQziqrLEk)
[How Kubernetes deprecations work with GKE](https://notifications.google.com/g/p/ACUgQrERXv5MBrkDdMVOfuZZXvErxkXag2tE-7nD3sh4FWYPVoqyExQYusYf_spDluqJpCfhz5-Z2evdyo9ggxZIcwnCX0XP8LQxiTCn_gyGcePZOpPBag22Ktk0CevQiCH0393xZv2INPvmxoKG7QwUrDzSyiZXl5wfYx-mn_pto4rnzsg0wqaCk5nngREybN6QNq7UOW9zsjjeYYh2peroIWSRZ7EvANTanZ66jqwxvg-irhzXZj_R1sHLFbbnHvAgH1m1j1_eSMAYetkXxCfoWiDG)
[Deprecated API migration guide for Kubernetes](https://notifications.google.com/g/p/ACUgQrFSV_4n1JiTBII_jaiE7w3XSVg9Sz_mOHR9gBzd_S88iKaV26omudxXh1wtES38qmBT8nHSziwPrPE5CG_Q6qXrc8FLngx-vSWnK1YqERfyRqAAEgwDiEbcB4E5DPhsYBKUrfI8fM6TCkyds-_-EGq6L3K1gOEQGfgK8CsxYdgvHdm4Nldb73BG-VZ43k_T3IvipJIVGVjfM5-LDGZkPFIhaJYComfzxXlK4iIiJhW_OaRxuOW7)
Thanks for choosing Google Kubernetes Engine.