k8s-multicluster

Manage Kubernetes multi-cluster context selection and cross-cluster operations via kubectl-mcp-server.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/spigell/my-agents --skill k8s-multicluster-spigell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-multicluster
Source: https://github.com/spigell/my-agents/tree/main/agents/shared/src/tools/ask_kubernetes_expert/skills/k8s-multicluster
Command: npx skills add https://github.com/spigell/my-agents --skill k8s-multicluster-spigell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the risk and friction of managing multiple Kubernetes clusters by helping you list contexts, switch safely, and run cross-cluster operations in a consistent, context-aware way.

Core Features & Use Cases

  • Context discovery and switching: List available kubeconfig contexts, view the active context, and switch contexts for the correct target cluster.
  • Cross-cluster querying and comparison: Compare namespaces across clusters and perform health checks by running kubectl-backed operations with an explicit context parameter.
  • Cluster API (CAPI) lifecycle tasks: List managed clusters and fetch kubeconfigs for workload clusters, with machine and deployment management for scaling.

Quick Start

Ask for a comparison of the production and staging namespaces for a specific resource type using explicit cluster contexts.

Frequently Asked Questions about k8s-multicluster

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

FAQPage Schema
How do I switch Kubernetes contexts safely across multiple clusters?

You can switch Kubernetes contexts safely by listing available kubeconfig contexts, viewing the active one, and selecting a new target context with an explicit context parameter.

Can I compare namespaces across different Kubernetes clusters?

Yes, you can compare namespaces across Kubernetes clusters by running kubectl-backed cross-cluster queries with an explicit context parameter for each environment.

What is the best way to run cross-cluster health checks in Kubernetes?

The best way to run cross-cluster health checks is to execute kubectl operations using an explicit context parameter for each cluster, ensuring context-aware and isolated query execution.

Does this support Cluster API lifecycle management for workload clusters?

Yes, it supports Cluster API lifecycle tasks by listing managed clusters, fetching kubeconfigs for workload clusters, and managing machines and deployments for scaling operations.

Do I need a specific kubeconfig setup to perform multi-cluster kubectl operations?

You need a valid kubeconfig containing multiple contexts to perform multi-cluster kubectl operations, as the workflow requires explicit context handling to target specific clusters.