gke-basics

Plan, provision, and configure production-grade GKE Autopilot clusters.

4|Updated Jul 16, 2012
One-click install
npx skills add https://github.com/takashabe/dotfiles --skill gke-basics-takashabe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gke-basics
Source: https://github.com/takashabe/dotfiles/tree/main/.claude/skills/gke-basics
Command: npx skills add https://github.com/takashabe/dotfiles --skill gke-basics-takashabe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Plan, provision, and configure production-grade Google Kubernetes Engine (GKE) clusters using a golden-path Autopilot configuration, covering Day-0 decisions, networking, security, observability, scaling, and cost optimization across AI/ML workloads.

Core Features & Use Cases

  • Golden-path Autopilot defaults and day-0 guardrails for secure, compliant clusters.
  • Networking, security, observability, and cost-optimization patterns for production GKE environments.
  • Use cases include cluster provisioning, upgrading, multi-tenancy, and AI/ML inference workloads on GKE.

Quick Start

Create a production-ready Autopilot GKE cluster using the golden-path defaults and verify cluster access.

Frequently Asked Questions about gke-basics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I provision a production-grade GKE cluster using Autopilot?

Provision a production-grade GKE cluster by applying golden-path Autopilot defaults that enforce private networking, Workload Identity, and RBAC hardening. This streamlines Day-0 decisions and provides secure, compliant cluster guardrails out of the box.

What is the best way to secure GKE clusters for multi-tenancy workloads?

Secure GKE multi-tenancy by implementing Workload Identity, Secret Manager integration, and RBAC hardening. These guardrails isolate tenant workloads while maintaining centralized observability and compliance across the cluster environment.

GKE Autopilot vs Standard: which cluster mode should I choose for AI/ML workloads?

Choose GKE Autopilot for AI/ML workloads to leverage managed node provisioning and built-in scaling guardrails, whereas Standard offers manual control over node configuration and networking for specialized inference requirements.

Does GKE Autopilot support private networking and Workload Identity by default?

Yes, GKE Autopilot supports private networking and Workload Identity. Applying golden-path defaults ensures these security features are configured correctly during cluster provisioning to meet production compliance requirements.

Can I run AI/ML inference workloads on GKE with cost optimization guardrails?

Run AI/ML inference workloads on GKE by combining Autopilot scaling patterns with cost optimization strategies. This configuration manages compute resource allocation dynamically while maintaining observability across the cluster.

What are the limitations of GKE Autopilot for cluster management?

GKE Autopilot limits manual node-level configuration and restricts certain privileged operations to maintain its managed golden-path guardrails. Evaluate Standard mode if your workflow requires custom node boot scripts or specific kernel-level tuning.