Kubernetes Skills
Manage multiple Kubernetes clusters, switch contexts, and perform cross-cluster operations. Use when working with multiple clusters, comparing environments, or managing cluster lifecycle.
Manage multiple Kubernetes clusters, switch contexts, and perform cross-cluster operations. Use when working with multiple clusters, comparing environments, or managing cluster lifecycle.
Real data. Real impact.
Emerging
Developers
Per week
Open source
Skills give you superpowers. Install in 30 seconds.
Cross-cluster operations and context management using kubectl-mcp-server's multi-cluster support.
list_contexts_tool()
kubeconfig_view() # Shows sanitized kubeconfig
CLI:
kubectl-mcp-server context <context-name>
All kubectl-mcp-server tools support the
context parameter:
# Get pods from production cluster get_pods(namespace="default", context="production-cluster")Get pods from staging cluster
get_pods(namespace="default", context="staging-cluster")
# Compare deployment across clusters compare_namespaces( namespace1="production", namespace2="staging", resource_type="deployment", context="production-cluster" )
Query multiple clusters simultaneously:
# Production cluster get_pods(namespace="app", context="prod-us-east") get_pods(namespace="app", context="prod-eu-west")Development cluster
get_pods(namespace="app", context="development")
# Check all clusters for context in ["prod-1", "prod-2", "staging"]: get_nodes(context=context) get_pods(namespace="kube-system", context=context)
For managing cluster lifecycle:
capi_clusters_list_tool(namespace="capi-system")
capi_cluster_get_tool(name="prod-cluster", namespace="capi-system")
capi_cluster_kubeconfig_tool(name="prod-cluster", namespace="capi-system")
capi_machines_list_tool(namespace="capi-system") capi_machinedeployments_list_tool(namespace="capi-system")
capi_machinedeployment_scale_tool( name="prod-cluster-md-0", namespace="capi-system", replicas=5 )
See CONTEXT-SWITCHING.md for detailed patterns.
Deploy charts to specific clusters:
install_helm_chart( name="nginx", chart="bitnami/nginx", namespace="web", context="production-cluster" )list_helm_releases( namespace="web", context="staging-cluster" )
flux_kustomizations_list_tool( namespace="flux-system", context="cluster-1" )flux_reconcile_tool( kind="kustomization", name="apps", namespace="flux-system", context="cluster-2" )
argocd_apps_list_tool(namespace="argocd", context="management-cluster")
# Read from source cluster get_secrets(namespace="app", context="source-cluster")Apply to target cluster (via manifest)
apply_manifest(secret_manifest, namespace="app", context="target-cluster")
With Cilium ClusterMesh or Istio multi-cluster:
cilium_nodes_list_tool(context="cluster-1") istio_proxy_status_tool(context="cluster-2")
Naming Convention: Use descriptive context names
prod-us-east-1, staging-eu-west-1Access Control: Different kubeconfigs per environment
Always Specify Context: Avoid accidental cross-cluster operations
# Explicit is better get_pods(namespace="app", context="production")
Cluster Groups: Organize by purpose
prod-*staging-*dev-*No automatic installation available. Please visit the source repository for installation instructions.
View Installation Instructions1,500+ AI skills, agents & workflows. Install in 30 seconds. Part of the Torly.ai family.
© 2026 Torly.ai. All rights reserved.