cloud-kubernetes-integrator_skill

Overview

This skill integrates Kubernetes workloads with managed cloud platforms (AWS EKS, Azure AKS, GCP GKE), handling IAM, ingress, storage classes, autoscaling, and platform-specific features. It produces concrete Kubernetes manifests and cloud-binding configs for service accounts, storage, ingress controllers, autoscalers, monitoring, and registry authentication. The outputs are validation-ready YAML and a checklist for basic, production, and advanced integration tiers.

How this skill works

Given cloud_provider, cluster_name, region, and optional ingress_type or autoscaling preferences, the skill validates inputs and selects cloud-native defaults. It generates IAM-to-Kubernetes ServiceAccount bindings, storage class manifests, ingress controller installation/configuration, autoscaler definitions, monitoring integrations, and registry auth. Tiers control depth: T1 covers IAM and storage; T2 adds ingress, autoscaling, monitoring and registry auth; T3 extends to HA, advanced autoscaling and disaster recovery.

When to use it

• Deploying stateful or stateless apps to managed clusters (EKS/AKS/GKE) requiring cloud IAM integration
• Setting up cloud-native ingress with SSL, health checks, and routing
• Configuring persistent storage with encryption and reclaim policies
• Enabling cluster autoscaling and cluster-level scaling policies
• Integrating cloud monitoring, logging, and container registry authentication

Best practices

• Prefer cloud-native identity (IRSA / Workload Identity) over static credentials for least-privilege access
• Use encrypted storage classes with explicit reclaimPolicy and allowVolumeExpansion set
• Select the cloud-native ingress controller by default unless advanced routing requires NGINX/Traefik
• Define min/max node counts and target utilization for autoscalers; include cost estimates for T2+
• Apply network policies, private VPC/VNet integration, and pod security standards for production clusters

Example use cases

• T1: Create an AWS IRSA-bound ServiceAccount and a gp3 EBS StorageClass for a stateful app
• T2: Install AWS Load Balancer Controller, enable Cluster Autoscaler, and configure CloudWatch Container Insights
• T2: Configure AKS with Workload Identity, Application Gateway Ingress Controller, and ACR integration
• T3: Deploy multi-AZ node pools, KEDA-based custom-metric autoscaling, and Velero backups to cloud storage
• Migration: Convert on-prem Kubernetes manifests to cloud-integrated manifests with registry auth and network rules