Add Kubernetes deployment templates

[PAMulligan]

Description

Add Kubernetes deployment manifests as a deployment option for enterprise and self-hosted environments. This complements the existing Docker support with production-grade orchestration templates.

Why

Enterprise teams deploying to EKS, GKE, or AKS need Kubernetes manifests. The existing Dockerfile provides the container — Kubernetes templates provide the orchestration layer (scaling, health checks, resource limits, ingress).

Acceptance Criteria

• Create `templates/kubernetes/` directory with:
  • `deployment.yaml` — Pod spec with health probes, resource limits, env vars from secrets
  • `service.yaml` — ClusterIP service
  • `ingress.yaml` — Ingress with TLS (nginx-ingress compatible)
  • `configmap.yaml` — Non-sensitive configuration
  • `secret.yaml` — Template for database credentials (with instructions)
  • `hpa.yaml` — Horizontal Pod Autoscaler
• Include proper health check probes (liveness and readiness on `/health`)
• Add resource requests/limits based on typical API workloads
• Add `--kubernetes` flag to `setup-project.sh` that copies these manifests
• Create a `kustomize/` overlay structure for staging/production
• Document how to deploy with `kubectl apply` and `kustomize`
• CI passes

Notes

This builds on the existing Docker templates. The Dockerfile remains the same — Kubernetes manifests orchestrate the container.

[github-actions]

This issue has been automatically marked as stale because it has not had any activity in the last 60 days. It will be closed in 14 days if no further activity occurs. If this issue is still relevant, please leave a comment or remove the stale label. Maintainers can add the pinned label to exempt an issue from being auto-closed. Thank you for your contributions!