This page explains how Kubernetesfeature gates function in Google Kubernetes Engine (GKE). Feature gates are a set of key-valuepairs that toggle Kubernetes features. You can modify Kubernetes featuregates in GKE only with alpha clusters. For more information, seeAlpha clusters.

The Kubernetes project releases new features instages over time. Features can be in thealpha,beta, orGA stage.

To see what features are enabled for your cluster running version 1.26 or later,check the feature gate state.

Alternatively, to verify the stage of a feature corresponding to the version ofyour cluster's control plane or nodes, check theFeature gates for Alpha orBetafeatures table in the Kubernetes documentation.

GA Kubernetes features in GKE

GA (also referred to asstable) Kubernetes features areenabled onGKE by default andcannot be disabled.

Beta Kubernetes features in GKE

Beta features are usuallyenabled by default in GKE.GKE might disable a specific beta feature for a particularversion to mitigate a known issue with the feature, to ensure backwardscompatibility, or because integration and qualification of the feature inGKE is not yet complete.

If you want to use a beta Kubernetes feature in your GKE clusterrunning version 1.26 or later, check that this feature is enabled bycheckingthe feature gate state. If your cluster is running aversion earlier than 1.26, you can check if the feature is enabled by testingthe feature.

Contact Cloud Customer Care if you can't verify whether the betafeature is enabled for your GKE cluster's control plane or nodeversion.

Kubernetes beta APIs with GKE clusters

In addition to beta Kubernetes features, you can also use Kubernetes beta APIswith GKE clusters. For beta APIs that were introduced withversion 1.24 or later, you must configure beta APIs per resource per cluster.For more information, seeUse Kubernetes beta APIs with GKEclusters.

Alpha Kubernetes features in GKE

Alpha Kubernetes features are disabled by default in all GKEclusters, except foralphaclusters. GKEmight enable a specific alpha feature in a specific control plane version.

With alpha clusters, all alpha feature gates available with the Kubernetesversion are enabled, and some beta feature gates, depending on the defaultvalue, are enabled. For more information about which feature gates are availablewith specific versions, and which beta features are enabled by default, seeFeature gates for Alpha or Beta featuresin the Kubernetes documentation. You can also selectively modify specificfeature gates. For more information, seeFeature gates and alphaclusters.

To enable all alpha Kubernetes features, create analpha Standard cluster.

1. Install and configure kubectl access

2. Run the following command:

   kubectlget--raw/metrics|grepkubernetes_feature_enabled

   The output, like in the following example, shows you the name of the featuregate, the corresponding stage ("" is GA), and whether the feature gate isenabled.1 means enabled and0 means disabled.

   See the following example output:

   # HELP kubernetes_feature_enabled [BETA] This metric records the data about the stage and enablement of a k8s feature.# TYPE kubernetes_feature_enabled gaugekubernetes_feature_enabled{name="APIListChunking",stage=""} 1kubernetes_feature_enabled{name="APIPriorityAndFairness",stage=""} 1kubernetes_feature_enabled{name="APIResponseCompression",stage="BETA"} 1kubernetes_feature_enabled{name="APISelfSubjectReview",stage=""} 1kubernetes_feature_enabled{name="APIServerIdentity",stage="BETA"} 1kubernetes_feature_enabled{name="APIServerTracing",stage="BETA"} 1kubernetes_feature_enabled{name="AdmissionWebhookMatchConditions",stage="BETA"} 1...

   This output indicates that, for example, theAPIResponseCompressionfeature is enabled and in the beta stage.

What's next

• For a complete list of current Kubernetes features, seeFeaturegates.
• For a full list of GKE features, refer to theGKE release notes.