Paste one or more ----separated Kubernetes manifests and get a plain-language summary of each resource (replicas, container images/ports, Service type/selector, ConfigMap/Secret key names — never Secret values — Ingress hosts, PVC storage), plus rule-based findings: unpinned image tags, missing resources.requests/limits, missing liveness/readiness probes, privileged/root/hostNetwork flags, a single-replica Deployment, a NodePort Service. Fixed rules, not an LLM. Parsing happens server-side (there's no practical way to parse full YAML in browser JS) — nothing is stored, the request/response is the only place it exists, same as the YAML ↔ JSON Converter.
curl -sS -X POST https://devops.majbase.com/k8s-yaml-explainer/api -H "Content-Type: application/json" --data-binary @- <<'EOF'
{"yaml": "apiVersion: apps/v1\nkind: Deployment\nmetadata:\n name: web\nspec:\n replicas: 1\n template:\n spec:\n containers:\n - name: app\n image: myapp"}
EOF
Returns {"resources": [...], "problems": [...], "counts": {...}, "total_resources": N, "total_problems": N}, or {"error": "..."}.