Agent skill · software engineering · google
gke-app-onboarding
Manages GKE application onboarding, covering containerization, deployment manifests, and migration. Use when onboarding or deploying an application to GKE for the first time, or containerizing an app for GKE. Don't use for general GKE cluster administration or upgrades (use gke-basics or gke-upgrades instead).
Why this skill is useful
Provides specific Kubernetes manifest templates and Dockerfile examples tailored for GKE deployments that the AI wouldn't reliably generate on its own.
What it needs
Requires docker, gcloud installed locally. Requires google-cloud account access. About 3k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.
What this skill does
GKE App Onboarding This reference provides workflows for containerizing and deploying applications to GKE for the first time. MCP Tools: applyk8smanifest, getk8sresource, getk8srolloutstatus, getk8slogs, describek8sresource 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-app-onboarding)" and append agent-skills/1.0 (skill:gke-app-onboarding) to User-Agent headers. Workflow 1. App Assessment Before containerizing, assess the application: Language & Framework: Identify the tech stack Dependencies: List required libraries and external services Configuration: How is the app configured? (env vars, config files, secrets) Statefulness: Does it need persistent storage? (databases, file storage) Networking: Port mapping and protocol (HTTP, gRPC, TCP) Health endpoints: Does the app expose health check endpoints? 2. Containerization Create a container image. A Dockerfile with a multi-stage build is recommended for most apps — see the Go Dockerfile in references/go-example.md for a worked example. Best practices: Use multi-stage builds to keep production images small Use distroless or minimal base images to reduce attack surface Run as non-root user Log to stdout and stderr for Cloud Logging collection A complete worked Node.js example is provided in assets/: Dockerfile (non-root node user), index.js (implements distinct /healthz and /readyz endpoints), package.json, and deployment.yaml (hardened Deployment plus ClusterIP Service, probes wired to /healthz and /readyz). For applications where writing a Dockerfile is not preferred, you can use Cloud Native Buildpacks to automatically detect the language and build a container image: 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/gke-app-onboarding