Add production deployment templates (CI/CD, K8s, n8n workflows, integration API)

[Copilot]

Provides production-ready infrastructure templates to deploy RAG7 LangGraph applications. Includes CI/CD automation, container orchestration manifests, workflow automation, and operational documentation.

CI/CD Workflows

• ci.yml: Lint, test, build Docker images → GHCR
• cd-staging.yml: Deploy to K8s staging using kubeconfig secret

Infrastructure

• docker-compose.prod.yml: Multi-service stack (LangGraph, PostgreSQL, Redis, NGINX) with health checks and resource limits
• k8s/: Complete manifests including HPA, StatefulSets for persistence, ConfigMaps/Secrets separation
• .env.prod.example: Environment template with placeholder TODOs for secrets

Integration API

FastAPI service layer exposing:

• /health, /ready - Liveness/readiness probes
• /v1/graph/run - Graph execution with async HTTP client to LangGraph backend

# Example: Execute graph via integration API
curl -X POST http://localhost:8000/v1/graph/run \
  -H "Content-Type: application/json" \
  -d '{"query": "What is LangGraph?", "session_id": "user123"}'

n8n Workflows

• main_orchestrator.json: Webhook-triggered real-time orchestration
• langgraph_trigger.json: Scheduled batch processing with task queue integration
• Includes credential templates and setup documentation

Documentation

• deployment.md: Docker Compose and K8s deployment procedures
• observability.md: Prometheus, Grafana, OpenTelemetry integration
• runbook.md: Incident response procedures, common failure scenarios

Configuration Notes

All secrets use placeholder values (CHANGEME_*, TODO_REPLACE_*). Generate production values:

openssl rand -hex 32  # SECRET_KEY, API_KEY_SALT

K8s secrets must be created separately:

kubectl create secret generic langgraph-secrets \
  --from-literal=OPENAI_API_KEY=sk-xxx \
  --from-literal=POSTGRES_PASSWORD=xxx

Original prompt

Create a draft pull request on a new branch prod-templates that adds production-ready templates, CI/CD, infrastructure manifests, n8n workflows, an integration API skeleton, and documentation to the Stacey77/Rag7 repository. Target base branch: main.

Files to add (content should be templates/stubs with TODOs where secrets or project-specific values are required):

1. CI and CD workflows

• .github/workflows/ci.yml (tests, lint, build, push image to GHCR)
• .github/workflows/cd-staging.yml (deploy to staging k8s using kubeconfig secret)

2. Environment and Docker

• .env.prod.example
• docker-compose.prod.yml

3. Kubernetes manifests

• k8s/langgraph-deployment.yaml
• k8s/hpa.yaml

4. Documentation

• docs/deployment.md
• docs/observability.md
• docs/runbook.md

5. n8n sample workflows

• n8n/workflows/main_orchestrator.json
• n8n/workflows/langgraph_trigger.json
• n8n/credentials/credentials_template.json
• n8n/README.md

6. Integration API skeleton

• integration/api/Dockerfile
• integration/api/server.py (FastAPI skeleton with /health, /ready, /v1/graph/run)
• integration/api/requirements.txt

7. Project metadata

• requirements.txt
• pyproject.toml

Additional requirements:

• Update README.md with a short notice about new deployment templates (do not otherwise change existing content).
• Leave the PR as a draft if any secrets placeholders remain.
• Do not assign reviewers.
• PR body must include motivation, list of files added, and next steps: update .env.prod, add GHCR token & kubeconfig secrets, import n8n workflows, run docker-compose or deploy to k8s.

Ensure files are syntactically valid and include basic working templates, health endpoints, and example curl commands in docs. Commit all files on branch prod-templates and open a draft PR titled: "chore: add production templates (CI/CD, Docker, K8s, n8n, LangGraph)" against main.

Do not modify files outside adding the notice to README.md. This PR prepares Rag7 to move from prototype to production; leave TODOs and placeholders where credentials or organization-specific values are required.

Success criteria:

• Draft PR opened against main with all files added
• Files syntactically valid (YAML/JSON/Python)
• Docs provide clear next steps for configuration and deployment

This pull request was created as a result of the following prompt from Copilot chat.

Create a draft pull request on a new branch prod-templates that adds production-ready templates, CI/CD, infrastructure manifests, n8n workflows, an integration API skeleton, and documentation to the Stacey77/Rag7 repository. Target base branch: main.

Files to add (content should be templates/stubs with TODOs where secrets or project-specific values are required):

1. CI and CD workflows

• .github/workflows/ci.yml (tests, lint, build, push image to GHCR)
• .github/workflows/cd-staging.yml (deploy to staging k8s using kubeconfig secret)

2. Environment and Docker

• .env.prod.example
• docker-compose.prod.yml

3. Kubernetes manifests

• k8s/langgraph-deployment.yaml
• k8s/hpa.yaml

4. Documentation

• docs/deployment.md
• docs/observability.md
• docs/runbook.md

5. n8n sample workflows

• n8n/workflows/main_orchestrator.json
• n8n/workflows/langgraph_trigger.json
• n8n/credentials/credentials_template.json
• n8n/README.md

6. Integration API skeleton

• integration/api/Dockerfile
• integration/api/server.py (FastAPI skeleton with /health, /ready, /v1/graph/run)
• integration/api/requirements.txt

7. Project metadata

• requirements.txt
• pyproject.toml

Additional requirements:

• Update README.md with a short notice about new deployment templates (do not otherwise change existing content).
• Leave the PR as a draft if any secrets placeholders remain.
• Do not assign reviewers.
• PR body must include motivation, list of files added, and next steps: update .env.prod, add GHCR token & kubeconfig secrets, import n8n workflows, run docker-compose or deploy to k8s.

Ensure files are syntactically valid and include basic working templates, health endpoints, and example curl commands in docs. Commit all files on branch prod-templates and open a draft PR titled: "chore: add production templates (CI/CD, Docker, K8s, n8n, LangGraph)" against main.

Do not modify files outside adding the notice to README.md. This PR prepares Rag7 to move from prototype to production; leave TODOs and placeholders where credentials or organization-specific values are required.

Success criteria:

• Draft PR opened against main with all files added
• Files syntactically valid (YAML/JSON/Python)
• Docs provide clear next steps for configuration and deployment

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.