Avoid deploying workloads in the default namespace

低レベル 2手動レビューgke

説明

Avoid deploying GKE workloads in the default namespace. Use dedicated namespaces to separate applications, environments, or tenants so namespace level controls can be applied consistently. The benchmark marks this recommendation Manual.

チェック方法

監査方法: 手動レビュー

この推奨事項は自動ではチェックできません。--include-manual を指定すると、スキャン結果にこの手順付きで一覧表示されます。

Run the following command to identify resources currently deployed in the default namespace: kubectl get all,configmaps,secrets,pvc,ingress,serviceaccounts,networkpolicies -n default Review any returned resources and determine whether they are application, environment, or tenant workloads that should be moved to a dedicated namespace. GKE supports identifying workloads running in the default namespace and migrating them to dedicated namespaces to improve reliability and security.

修正方法

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

Create dedicated namespaces for workloads based on application, environment, or tenant boundaries, then migrate application resources out of the default namespace. Make updates so all workload resources explicitly specify the new target namespace. After migration, apply appropriate namespace level governance, including RBAC, ResourceQuotas, NetworkPolicies, Pod Security labels, and ownership labels.

プロパティ

オペレーティングシステム: すべて
タグ: gkepolicies
参照: CIS Google Kubernetes Engine (GKE) Benchmark v2.0.0 - 4.6.4 Avoid deploying workloads in the default namespace