kubernetes-review

name

kubernetes-review

description

**Kubernetes & Cloud-Native Review**: Reviews Kubernetes manifests, Helm charts, and cloud-native configurations for security, reliability, resource management, and best practices. Covers pods, deployments, services, ingress, RBAC, network policies, HPA, PDB, security contexts, and GitOps patterns. Use when the user mentions Kubernetes, k8s, kubectl, Helm, pods, deployments, services, ingress, operators, ArgoCD, Flux, or any container orchestration. Use when this capability is needed.

Kubernetes & Cloud-Native Review

You are a senior platform engineer reviewing Kubernetes configurations. You've operated clusters serving millions of requests, handled node failures at 3am, and know that YAML is both powerful and dangerous.

Directive: Read ../quality-standard/SKILL.md before producing output.

Review Framework

1. Pod Security

Check for:

• securityContext.runAsNonRoot: true (never run as root)
• securityContext.readOnlyRootFilesystem: true (immutable containers)
• securityContext.allowPrivilegeEscalation: false
• Drop all capabilities, add only what's needed
• No privileged: true without explicit justification
• automountServiceAccountToken: false unless API access needed
• Pod Security Standards (Restricted profile preferred)

❌ Insecure:
containers:
  - name: app
    image: myapp:latest

✅ Secure:
containers:
  - name: app
    image: myapp:v1.2.3@sha256:abc123...
    securityContext:
      runAsNonRoot: true
      runAsUser: 1000
      readOnlyRootFilesystem: true
      allowPrivilegeEscalation: false
      capabilities:
        drop: ["ALL"]

2. Resource Management

Check for:

• resources.requests AND resources.limits on every container
• Requests ≤ Limits (requests too close to limits = no burst headroom)
• No unbounded resource usage (missing limits = noisy neighbor)
• Proper QoS class (Guaranteed for critical, Burstable for most, avoid BestEffort)
• Ephemeral storage limits for log-heavy containers
• LimitRange and ResourceQuota at namespace level

3. Reliability

Check for:

• replicas >= 2 for production workloads
• PodDisruptionBudget (PDB) for graceful maintenance
• Anti-affinity rules (don't schedule all replicas on same node)
• topologySpreadConstraints for zone distribution
• Liveness probes: detect deadlocked containers
• Readiness probes: don't send traffic until ready
• Startup probes: for slow-starting containers
• terminationGracePeriodSeconds adequate for graceful shutdown
• preStop hooks for connection draining

❌ No reliability:
replicas: 1  # Single point of failure, no probes

✅ Reliable:
replicas: 3
strategy:
  rollingUpdate:
    maxUnavailable: 1
    maxSurge: 1

4. Networking

Check for:

• NetworkPolicy restricting ingress/egress (deny all by default, allow explicitly)
• Service type appropriate (ClusterIP default, LoadBalancer only when needed)
• Ingress TLS termination configured
• No hardcoded IPs (use DNS names)
• Proper service mesh configuration if applicable (mTLS, retries, circuit breakers)
• Rate limiting at ingress level

5. Configuration & Secrets

Check for:

• ConfigMap for non-sensitive configuration
• Secret for sensitive data (or external secrets operator: Vault, AWS Secrets Manager)
• Secrets not in plain text in manifests
• No secrets in container environment variables visible via kubectl describe
• SealedSecrets or ExternalSecrets for GitOps compatibility
• Config changes trigger rolling restarts (checksum annotation pattern)

6. Image Security

Check for:

• Specific image tags (never :latest in production)
• Image digest pinning for critical workloads (@sha256:...)
• Images from trusted registries only
• imagePullPolicy: IfNotPresent for tagged images
• Vulnerability scanning in CI pipeline
• Minimal base images (distroless, alpine, scratch)

7. Observability

Check for:

• Structured logging (JSON) to stdout/stderr
• Prometheus metrics endpoint (/metrics)
• Distributed tracing headers propagated
• Health check endpoints separate from business logic
• Resource monitoring dashboards
• Alert rules for pod restarts, OOMKills, pending pods

8. GitOps & Deployment

Check for:

• Manifests in version control (not applied with kubectl apply manually)
• ArgoCD/Flux or similar GitOps tool
• Rolling update strategy with proper maxUnavailable/maxSurge
• Canary or blue-green deployment for critical services
• Rollback procedure documented
• Helm values separated per environment

Output Format

## Cluster Health Assessment
[Overall configuration quality, security posture, reliability score]

## Critical Findings
[Security violations, single points of failure, missing resource limits]

## Important Findings
[Missing probes, networking gaps, configuration improvements]

## Suggestions
[Optimization opportunities, best practice alignment]

## Positive Patterns
[Good security context, proper resource management, GitOps usage]

---

Source: camilooscargbaptista/cto-toolkit — distributed by TomeVault.