kubernetes-cluster-onboarding

Map an unfamiliar Kubernetes cluster before making changes.

1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/Arafly/sre-playbooks --skill kubernetes-cluster-onboarding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kubernetes-cluster-onboarding
Source: https://github.com/Arafly/sre-playbooks/tree/main/kubernetes-cluster-onboarding
Command: npx skills add https://github.com/Arafly/sre-playbooks --skill kubernetes-cluster-onboarding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you understand an unfamiliar Kubernetes cluster before making changes, so you can avoid breaking traffic, ownership boundaries, or production workloads.

Core Features & Use Cases

  • Cluster Orientation: Identifies cluster purpose, version, node shape, controllers, and management model.
  • Namespace and Workload Mapping: Inventories deployments, services, ingresses, jobs, secrets, and critical namespaces.
  • Traffic and Risk Analysis: Traces request flow, checks RBAC, network policies, probes, resource limits, PDBs, and other operational hazards.
  • Safe Operational Guidance: Recommends read-only inspection first, then a low-risk fix or an escalation path when changes are unsafe.
  • Use Case: Use it when inheriting a new cluster, debugging an unknown namespace, or preparing a production change in a GitOps-managed environment.

Quick Start

Help me onboard this Kubernetes cluster by summarizing its structure, mapping the critical namespaces and workloads, tracing the main traffic path, and listing the biggest operational risks.

Frequently Asked Questions about kubernetes-cluster-onboarding

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

FAQPage Schema
How do I map an unfamiliar Kubernetes cluster before making changes?

To map an unfamiliar Kubernetes cluster, you should perform a read-only inspection of workloads, services, ingress, and network policies to produce a safe operational map and avoid breaking production traffic.

What is the best way to inventory namespaces and trace traffic in a GitOps-managed environment?

Inventorying namespaces and tracing traffic in a GitOps-managed environment requires inspecting deployments, services, and ingress paths to understand request flow and identify operational hazards before applying changes.

How does RBAC review work when inheriting a new Kubernetes cluster?

RBAC review during cluster onboarding involves checking role bindings and network policies to understand ownership boundaries and ensure safe operational guidance without violating access controls.

Can I assess production risks in an inherited cluster without breaking workloads?

Yes, you can assess production risks by conducting a read-only inspection of probes, resource limits, and Pod Disruption Budgets to identify operational hazards and establish an escalation path for unsafe changes.

When do I need to check rollback paths and resource limits during cluster onboarding?

You need to check rollback paths and resource limits during cluster onboarding when preparing a production change, ensuring you understand the cluster's management model and can safely navigate operational hazards.

What should I inspect to understand the management model of an unknown Kubernetes cluster?

To understand the management model of an unknown cluster, inspect the cluster version, node shape, controllers, and critical namespaces to identify its purpose and GitOps configuration before making modifications.