k8s-management

Inspect Kubernetes cluster status, logs, and resources via read-only kubectl commands.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/SerendipityOneInc/srp-claude-code-marketplace --skill k8s-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-management
Source: https://github.com/SerendipityOneInc/srp-claude-code-marketplace/tree/main/plugins/srp-devops/skills/k8s-management
Command: npx skills add https://github.com/SerendipityOneInc/srp-claude-code-marketplace --skill k8s-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides read-only Kubernetes cluster inspection and monitoring capabilities, enabling teams to quickly assess pod health, resource usage, and service status without making changes to the cluster.

Core Features & Use Cases

  • Pod status, logs, and resource usage across namespaces to aid on-call troubleshooting.
  • Service andDeployment health checks and basic cluster information for capacity planning.
  • Read-only operational workflows that support auditing and incident response without modifying state.

Quick Start

Try common read-only commands to inspect a cluster and diagnose issues.

  • List pods: kubectl get pods -n <namespace>
  • Describe a pod: kubectl describe pod <pod-name> -n <namespace>
  • View pod logs: kubectl logs <pod-name> -n <namespace>
  • Get cluster info: kubectl cluster-info
  • Show node resource usage: kubectl top nodes

Frequently Asked Questions about k8s-management

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

FAQPage Schema
How do I check pod status and logs across Kubernetes namespaces?

Pod status and logs are retrieved using kubectl commands scoped to specific namespaces. Use `kubectl get pods -n <namespace>` to list pods, `kubectl describe pod <pod-name> -n <namespace>` for detailed status, and `kubectl logs <pod-name> -n <namespace>` to view logs. This read-only inspection aids on-call troubleshooting without modifying cluster state.

Can I monitor Kubernetes cluster health and resource usage without making changes?

Yes, read-only kubectl commands provide cluster inspection capabilities. Use `kubectl cluster-info` for basic cluster information, `kubectl top nodes` to show node resource usage, and inspect services and deployments for health checks. These operations support auditing and incident response workflows while maintaining RBAC read-only constraints.

What kubectl commands are needed for Kubernetes cluster troubleshooting and capacity planning?

Kubernetes troubleshooting and capacity planning rely on read-only kubectl inspection: `kubectl get pods` and `kubectl describe pod` diagnose pod issues, `kubectl logs` retrieves application output, and `kubectl top nodes` reveals resource utilization. Service and deployment health checks assess cluster capacity without state modification.

How do I set up read-only Kubernetes access for DevOps workflows?

Read-only Kubernetes access is configured through RBAC permissions that restrict kubectl commands to inspection operations across namespaces. This enables DevOps teams and on-call staff to query pod status, view logs, check service health, and assess node resources for troubleshooting and capacity planning without write permissions.

Does namespace scoping work with kubectl monitoring commands?

Yes, namespace scoping is integral to kubectl operations. The `-n <namespace>` flag restricts pod status, logs, describes, and resource queries to specific namespaces, enabling teams to isolate troubleshooting and monitoring within designated cluster segments while respecting RBAC read-only constraints.