Do not use GKE alpha clusters for production workloads

How it is checked

Audit method: Shell command

v=$(gcloud container clusters describe "${GKE_CLUSTER:?set GKE_CLUSTER}" --location "${GKE_LOCATION:?set GKE_LOCATION}" ${GKE_PROJECT:+--project=$GKE_PROJECT} --format='value(enableKubernetesAlpha)') || exit 1
if [ "$v" != True ]; then echo compliant; else echo "noncompliant: enableKubernetesAlpha=$v"; fi

Expected output

compliant

How it is fixed

Fix method: Guidance or infrastructure patch

Alpha cluster behavior is selected at cluster creation and should not be used for production workloads. To remediate a production workload running on an alpha cluster, create a supported non alpha GKE cluster, migrate workloads and required data, validate application health, and decommission the alpha cluster. Alpha clusters expire after 30 days, do not receive security updates, cannot be upgraded, and are not covered by the GKE SLA. gcloud container clusters create $CLUSTER_NAME \ --location $LOCATION \ --project $PROJECT_ID Do not include the --enable-kubernetes-alpha flag when creating the replacement production cluster. If alpha features are needed for testing, use a separate nonproduction alpha cluster and migrate any required data before the 30 day expiration window.

Check this host

Run this on a machine you are allowed to audit. The scan is read-only.

tmaegis scan --target gke