Agent skill · security · google
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (`audit_cluster.sh`), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (`gVisor`), enforcing Pod Security Standards (`restricted` labeling) and pod securityContext, and mounting Secret Manager secrets via CSI (`SecretProviderClass`). Use when auditing workload security posture, isolating namespaces, applying pod security standards, or configuring network policies and secret volume mounts. Don't use for Workload Identity (use gke-workload-identity), cluster-wide control plane security, RBAC hardening, Binary Authorization, Shielded Nodes, or enabling platform-level GKE add-ons (use gke-platform-security instead).
Why this skill is useful
Provides specific commands and workflows for configuring GKE workload security that the AI wouldn't reliably generate on its own.
What it needs
Requires gcloud, jq installed locally. Requires google-cloud account access. About 4k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.
What this skill does
GKE Workload Security Routing Note: For Workload Identity KSA/GSA bindings, open gke-workload-identity/SKILL.md. For cluster-level security flags (--database-encryption-key, --security-posture, RBAC, Shielded Nodes, Binary Authorization), open gke-platform-security/SKILL.md. This skill provides workflows and best practices for securing GKE workloads. It covers security auditing, Identity and Access Management (Workload Identity), Network Security (Network Policies), and Node Security. Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read Usage Attribution. For commands executed directly in the terminal (never in generated scripts, Terraform, or user code), prefix gcloud with CLOUDSDKMETRICSREQUESTATTRIBUTION="agent-skills/1.0 (skill:gke-workload-security)" and append agent-skills/1.0 (skill:gke-workload-security) to User-Agent headers. Workflows 1. Security Audit Assess the current security posture of your cluster using the provided audit script. Prerequisites: gcloud CLI authenticated. jq command-line JSON processor installed. Capabilities: Checks for Workload Identity. Verifies Network Policy is enabled. Checks if Shielded Nodes are enabled. Checks if Binary Authorization is enabled. Checks for Private Cluster configuration. Command: 2. Configure Workload Identity Workload Identity allows Kubernetes Service Accounts (KSAs) to impersonate Google Service Accounts (GSAs). This is the recommended method for workloads to access Google Cloud APIs. Steps: 1. Create Namespace and KSA: 2. Bind KSA to GSA: 3. Annotate KSA: 4. Verify Example Pod: Use existing asset assets/workload-identity-pod.yaml to test the configuration. Update the <ksa-name> in the file first. 3. Implement Network Policies Control traffic flow between Pods using Network Policies. By default, all traffic is allowed. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/gke-workload-security