Kubernetes 1.32 deprecated APIs

This page explains how to prepare clusters for upgrades to GKEversion 1.32. You can find API clients making calls todeprecated APIs removedin1.32and update those clients to use GA APIs. For more detailed information, see theKubernetes deprecated API migrationguide.

Removed APIs in version 1.32

The deprecated APIs in Kubernetes version 1.32 are either Beta APIs that havegraduated to GA (for examplev2) or from one Beta version to another (forexample,v1beta1 tov1beta2). The GA APIs providelonger-term compatibilityguaranteesand should be used in place of the deprecated Beta APIs.

All existing objects for APIs that have graduated to new versions can beinteracted with by using the updated APIs.

Important: Before upgrading to 1.32, you should update API clients and manifeststo use the updated APIs.

Flow control resources

Theflowcontrol.apiserver.k8s.io/v1beta3 API version of FlowSchema andPriorityLevelConfiguration is no longer served as of v1.32.

Migrate manifests and API clients to use theflowcontrol.apiserver.k8s.io/v1API version, available since v1.29.

All existing persisted objects are accessible with the new API.

Theflowcontrol.apiserver.k8s.io/v1 API version has the following notablechanges:

  • The PriorityLevelConfigurationspec.limited.assuredConcurrencyShares fieldis renamed tospec.limited.nominalConcurrencyShares and only defaults to30 when unspecified, and an explicit value of 0 is not changed to 30.

Preparing to upgrade to version 1.32

You don't need to delete and recreate any of your API objects. All existingpersisted API objects for APIs that graduated to GA can already be read andupdated using the new API versions.

However, we recommend that you migrate your clients and manifests beforeupgrading to Kubernetes 1.32. To learn more, seeKubernetes Deprecated APIMigrationGuide.

You canview deprecation insights andrecommendationsto determine if your cluster is using Kubernetes 1.32 deprecated APIs.GKE generates deprecation insights when user agents calldeprecated APIs, not from the configuration of your Kubernetes objects.

Warning: If you don't update a client or manifest before the 1.32 upgrade, itwon't be able to read or modify existing objects or create new objects. Theclient or manifest will only be able to read, modify, or create objects once youupdate it.

Find clusters using deprecated APIs

You can find which clusters are using deprecated APIs fromdeprecation insights. Deprecationinsights also provide information such as which API clients are callingthe deprecated APIs in your cluster.

You can also use audit logs to find which clients are making calls to deprecatedAPIs.

Locate API clients making write calls to deprecated APIs

For clusters with Google Cloud Observability enabled, you can use the followingAdmin Activity audit logquery to show the use of deprecated APIs by user agents that are notGoogle-managed:

resource.type="k8s_cluster"labels."k8s.io/removed-release"="DEPRECATED_API_MINOR_VERSION"protoPayload.authenticationInfo.principalEmail:("system:serviceaccount" OR "@")protoPayload.authenticationInfo.principalEmail!~("system:serviceaccount:kube-system:")

ReplaceDEPRECATED_API_MINOR_VERSION with the minorversion where the deprecated API is removed, for example1.22.

Admin Activity audit logs are automatically enabled for GKEclusters. With this query, the logs show user agents making write calls to thedeprecated APIs.

Locate API clients making read calls to deprecated APIs

By default, audit logs show only write calls to the deprecated APIs. To alsoshow read calls to deprecated APIs, configure Data Access audit logs.

Caution: If you enable additional audit logs, this might incur additionallogging costs. The volume of ingested Data Access auditlogs counts toward the Cloud Logginglogs ingestion quota.

Follow the instructions toConfigure Data Access audit logs with the Google Cloud console. In the Google Cloud console, select the Kubernetes Engine API. In the Log Types tab in the information panel,selectAdmin Read andData Read.

With these logs enabled, you can now use the original query to see both readcalls and write calls to the deprecated APIs.

Upgrading third-party components

Deprecation insightsmight display results for third-party agents that make calls to deprecated APIsin your cluster.

To resolve third-party agents calling deprecated APIs, we recommend thefollowing best practices:

  1. Check with your third-party software provider for an updated version.
  2. Upgrade the third-party software to the latest version. If you cannotupgrade the software, you should test whether upgrading GKEto the version with the removed deprecated APIs would break your service.

We recommend that you perform this upgrade and the GKE versionupgrade on a staging cluster to monitor for disruptions before you upgrade yourproduction clusters.

Update clusters impacted by deprecations

GKE pauses automatic upgrades for clusters impacted bydeprecations. To learn more, seeHow Kubernetes deprecations work withGKE.

To upgrade clusters impacted by deprecations, perform the following steps:

  1. Check which user agents use the deprecated APIs in thelogs.
  2. Update the user agents that use the deprecated APIs to use supported APIversions.
  3. Update any third-party software that calls deprecated APIs to the latestversions.
  4. Upgrade a test cluster and test your application in a testing environmentbefore upgrading your production cluster to reduce the risk of disruptionswhen deprecated APIs are no longer available.

  5. If you can't update an affected user agent, upgrade a separate test clusterto check whether the upgrade causes disruptions. If the upgrade doesn'tcause disruptions, you canupgrade your clustermanually.

  6. After you update all of the user agents, GKE waits until ithas no longer observed use of deprecated APIs for 30 days, and then unblocksautomatic upgrades. Automatic upgrades proceed according to thereleaseschedule.

Resources

More information is available in the OSS Kubernetes documentation:

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-18 UTC.