What problem does it solve?
Operations engineers often struggle with manually managing Kubernetes resources across multiple cloud-hosted clusters, facing risks of human error, inconsistent workflows, and accidental production outages when switching between different cluster contexts.
Core Features & Use Cases
- Multi-cluster resource management: View status of Pods, Deployments, Services, Nodes and other K8s resources across AWS EKS, GCP GKE, and Azure AKS clusters without modifying global kubectl context.
- Troubleshooting support: Check pod logs, events, exec into containers, and set up port-forwards to quickly diagnose issues like CrashLoopBackOff or network connectivity problems.
- Safe change operations: Perform scaling, rollout restarts, configuration applies, and other modifications with mandatory user confirmation to prevent unintended changes to production environments.
- Use case example: If your team's payment service on the production EKS cluster is experiencing downtime, you can use this skill to check pod status, view error logs, and safely restart the deployment after confirming the operation with your team.
Quick Start
Use the k8s-ops skill to check the status of all pods in the staging cluster's default namespace and view the last 100 lines of logs for the pod named api-gateway that is in a CrashLoopBackOff state.