510 Kubernetes Troubleshooting 5f5d9509

Name: 510 Kubernetes Troubleshooting 5f5d9509
Author: tools-only

ASecurity

```bash kubectl get pods -o wide kubectl get events -n <namespace> --sort-by='.lastTimestamp'

9 stars
0 votes
0 copies
0 views
Added October 11, 2026

devopsbashnodekubernetesdebugging

Security analysis

A96/100

mediumUses curl or wget to download content

Pro shows the line behind each finding and how to fix it

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 510-kubernetes-troubleshooting_5f5d9509 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 510 Kubernetes Troubleshooting 5f5d9509?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 510 Kubernetes Troubleshooting 5f5d9509

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-510-kubernetes-troubleshooting-5f5d9509/badge)](https://www.skillsdirectory.com/skills/tools-only-510-kubernetes-troubleshooting-5f5d9509)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md

# Kubernetes Troubleshooting

## Debugging Workflow

```bash
# 1. Overview
kubectl get pods -o wide
kubectl get events -n <namespace> --sort-by='.lastTimestamp'

# 2. Details
kubectl describe pod <pod-name>

# 3. Logs
kubectl logs <pod-name>
kubectl logs <pod-name> --previous  # Crashed instance
kubectl logs <pod-name> -c <container>
```

## Common Pod States

| State | Cause | Solution |
|-------|-------|----------|
| Pending | No node resources | Check node capacity |
| ContainerCreating | Image pulling | Check image URI |
| CrashLoopBackOff | Container exits | Check logs, health checks |
| ImagePullBackOff | Failed image pull | Verify credentials |
| OOMKilled (137) | Out of memory | Increase memory limit |

## Service & Network

```bash
kubectl exec -it <pod-name> -- nslookup kubernetes.default
kubectl exec -it <pod-name> -- curl http://myservice:8080
kubectl get endpoints <service-name>
kubectl port-forward service/myservice 8080:8080
kubectl get networkpolicies -A
```

## Quick Fixes

| Problem | Command |
|---------|---------|
| Pod stuck | `kubectl delete pod <name> --grace-period=0 --force` |
| High CPU | `kubectl top pods -A --sort-by=cpu` |
| High memory | `kubectl top pods -A --sort-by=memory` |
| Restart | `kubectl rollout restart deployment/<name>` |
| Rollback | `kubectl rollout undo deployment/<name>` |

See `kubernetes-troubleshooting-advanced.md` for node issues, HPA, anti-patterns.