Use VPC native GKE clusters with alias IP address ranges

中レベル 1自動gke

説明

Use VPC native GKE clusters with alias IP address ranges so Pod and Service IP addresses are allocated from subnet secondary IP address ranges in the cluster’s VPC network. This provides native VPC routing for GKE workloads and avoids relying on custom static routes for Pod routing. Requires gcloud with container.clusters.get; the cluster comes from GKE_CLUSTER and GKE_LOCATION (optional GKE_PROJECT, else the gcloud default project).

チェック方法

監査方法: シェルコマンド

shell

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

期待される出力: compliant

修正方法

修正方法: ガイダンスまたは IaC パッチ

VPC native networking is selected at cluster creation and cannot be enabled on an existing routes based cluster. To remediate a noncompliant cluster, create a new GKE cluster with alias IP address ranges enabled, migrate workloads to the new cluster, validate application connectivity, and decommission the routes based cluster after migration is complete. gcloud container clusters create $CLUSTER_NAME \ --location $LOCATION \ --project $PROJECT_ID \ --enable-ip-alias For production clusters, define or select appropriate subnet secondary IP address ranges for Pods and Services before cluster creation. Proper IP range planning helps avoid Pod or Service IP exhaustion as the cluster scales. • Note: VPC native networking is selected at cluster creation and cannot be enabled on an existing routes based cluster.

プロパティ

オペレーティングシステム: すべて
タグ: gkemanaged-servicesnetwork
参照: CIS Google Kubernetes Engine (GKE) Benchmark v2.0.0 - 5.6.2 Use VPC native GKE clusters with alias IP address ranges

このホストをチェック

監査が許可されているマシンで実行してください。スキャンは読み取り専用です。

shell

tmaegis scan --target gke