원클릭으로 Manus에서 모든 스킬 실행

kubernetes

Kubernetes/EKS patterns. Use when managing deployments, pods, troubleshooting containers, viewing logs, or scaling applications.

Manus에서 실행

개요

Kubernetes/EKS patterns. Use when managing deployments, pods, troubleshooting containers, viewing logs, or scaling applications.

설치 명령

npx skills add https://github.com/arvoreeducacao/rhm --skill kubernetes

이 명령을 Claude Code에 복사하여 붙여넣어 스킬을 설치하세요

출처

arvoreeducacao/rhm

스타14

포크2

업데이트2026년 2월 17일 20:29

SKILL.md

readonly

name	kubernetes
description	Kubernetes/EKS patterns. Use when managing deployments, pods, troubleshooting containers, viewing logs, or scaling applications.
triggers	["kubernetes","k8s","kubectl","pods","deployments","eks","containers","cluster"]

Kubernetes Operations Guide

When to Use This Skill

Use when managing Kubernetes deployments, troubleshooting pod issues, viewing application logs, scaling services, or debugging container problems.

Common Operations

View Resources

kubectl get pods -n <namespace>
kubectl get pods -n <namespace> -o wide
kubectl get pods -n <namespace> -l app=<app-name>
kubectl get deployments -n <namespace>
kubectl get svc -n <namespace>
kubectl get ingress -n <namespace>
kubectl get all -n <namespace>

Logs

kubectl logs -n <namespace> <pod-name>
kubectl logs -n <namespace> <pod-name> -f
kubectl logs -n <namespace> <pod-name> --tail=100
kubectl logs -n <namespace> <pod-name> --previous
kubectl logs -n <namespace> -l app=<app-name> --all-containers=true
kubectl logs -n <namespace> <pod-name> --since=1h

Describe & Debug

kubectl describe pod -n <namespace> <pod-name>
kubectl describe deployment -n <namespace> <deployment>
kubectl get events -n <namespace> --sort-by='.lastTimestamp'
kubectl top pods -n <namespace>
kubectl top nodes

Execute Commands

kubectl exec -it -n <namespace> <pod-name> -- /bin/sh
kubectl exec -n <namespace> <pod-name> -- cat /app/config.json
kubectl port-forward -n <namespace> svc/<service> <local-port>:<remote-port>

Scaling

kubectl scale deployment -n <namespace> <deployment> --replicas=<n>
kubectl get hpa -n <namespace>
kubectl describe hpa -n <namespace> <hpa-name>

Rollouts

kubectl rollout restart deployment -n <namespace> <deployment>
kubectl rollout status deployment -n <namespace> <deployment>
kubectl rollout history deployment -n <namespace> <deployment>
kubectl rollout undo deployment -n <namespace> <deployment>

Troubleshooting

Pod in CrashLoopBackOff

Check logs from previous container: kubectl logs -n <ns> <pod> --previous
Check events: kubectl describe pod -n <ns> <pod>
Common causes: missing env vars, secret not synced, DB connection failed, OOMKilled

Pod in Pending

Check events: kubectl describe pod -n <ns> <pod>
Check node resources: kubectl top nodes
Common causes: insufficient CPU/memory, node selector mismatch, PVC not bound

Pod in ImagePullBackOff

Verify image exists: kubectl describe pod -n <ns> <pod> | grep -A5 "Image:"
Check registry authentication

Service Not Responding

Verify pods are running: kubectl get pods -n <ns> -l app=<app>
Check endpoints: kubectl get endpoints -n <ns> <service>
Test connectivity: kubectl run debug --rm -it --image=busybox -- wget -qO- http://<svc>.<ns>.svc.cluster.local

Best Practices

Always verify context before running commands
Use labels for filtering resources
Check events first when troubleshooting
Don't delete pods without understanding the impact
Use rollout restart instead of deleting pods
Scale gradually — don't jump from 2 to 20 replicas

이 저장소의 다른 Skills

같은 저장소

aws

arvoreeducacao/rhm

AWS infrastructure patterns. Use when working with AWS services, secrets, ECS/EKS, RDS, S3, CloudWatch, or debugging infrastructure issues.

2026-02-1714

backend-nestjs

arvoreeducacao/rhm

NestJS backend development patterns. Use when developing backend APIs with NestJS, TypeORM/Prisma, and TypeScript.

2026-02-1714

database-mysql

arvoreeducacao/rhm

MySQL database patterns. Use when querying database schema, exploring data, understanding table relationships, or debugging data issues.

2026-02-1714

frontend-nextjs

arvoreeducacao/rhm

NextJS frontend development patterns. Use when developing frontend code with NextJS, React, Tailwind, and TypeScript.

2026-02-1714

qa-test-planner

arvoreeducacao/rhm

QA test planning patterns. Use when creating test plans, writing test cases, building regression suites, validating designs against Figma, or documenting bugs.

2026-02-1714

출처

arvoreeducacao

arvoreeducacao/rhm

GitHub 저장소 열기 Creator 저장소 보기

설치 명령

다운로드

Manus에서 실행

유용한 대상SOC

네트워크·컴퓨터 시스템 관리자컴퓨터 및 수학직15-1244L4

name	kubernetes
description	Kubernetes/EKS patterns. Use when managing deployments, pods, troubleshooting containers, viewing logs, or scaling applications.
triggers	["kubernetes","k8s","kubectl","pods","deployments","eks","containers","cluster"]

Kubernetes Operations Guide

When to Use This Skill

Use when managing Kubernetes deployments, troubleshooting pod issues, viewing application logs, scaling services, or debugging container problems.

Common Operations

View Resources

kubectl get pods -n <namespace>
kubectl get pods -n <namespace> -o wide
kubectl get pods -n <namespace> -l app=<app-name>
kubectl get deployments -n <namespace>
kubectl get svc -n <namespace>
kubectl get ingress -n <namespace>
kubectl get all -n <namespace>

Logs

kubectl logs -n <namespace> <pod-name>
kubectl logs -n <namespace> <pod-name> -f
kubectl logs -n <namespace> <pod-name> --tail=100
kubectl logs -n <namespace> <pod-name> --previous
kubectl logs -n <namespace> -l app=<app-name> --all-containers=true
kubectl logs -n <namespace> <pod-name> --since=1h

Describe & Debug

kubectl describe pod -n <namespace> <pod-name>
kubectl describe deployment -n <namespace> <deployment>
kubectl get events -n <namespace> --sort-by='.lastTimestamp'
kubectl top pods -n <namespace>
kubectl top nodes

Execute Commands

kubectl exec -it -n <namespace> <pod-name> -- /bin/sh
kubectl exec -n <namespace> <pod-name> -- cat /app/config.json
kubectl port-forward -n <namespace> svc/<service> <local-port>:<remote-port>

Scaling

kubectl scale deployment -n <namespace> <deployment> --replicas=<n>
kubectl get hpa -n <namespace>
kubectl describe hpa -n <namespace> <hpa-name>

Rollouts

kubectl rollout restart deployment -n <namespace> <deployment>
kubectl rollout status deployment -n <namespace> <deployment>
kubectl rollout history deployment -n <namespace> <deployment>
kubectl rollout undo deployment -n <namespace> <deployment>

Troubleshooting

Pod in CrashLoopBackOff

Check logs from previous container: kubectl logs -n <ns> <pod> --previous
Check events: kubectl describe pod -n <ns> <pod>
Common causes: missing env vars, secret not synced, DB connection failed, OOMKilled

Pod in Pending

Check events: kubectl describe pod -n <ns> <pod>
Check node resources: kubectl top nodes
Common causes: insufficient CPU/memory, node selector mismatch, PVC not bound

Pod in ImagePullBackOff

Verify image exists: kubectl describe pod -n <ns> <pod> | grep -A5 "Image:"
Check registry authentication

Service Not Responding

Verify pods are running: kubectl get pods -n <ns> -l app=<app>
Check endpoints: kubectl get endpoints -n <ns> <service>
Test connectivity: kubectl run debug --rm -it --image=busybox -- wget -qO- http://<svc>.<ns>.svc.cluster.local

Best Practices

Always verify context before running commands
Use labels for filtering resources
Check events first when troubleshooting
Don't delete pods without understanding the impact
Use rollout restart instead of deleting pods
Scale gradually — don't jump from 2 to 20 replicas