Add Woodpecker CI pipeline and k8s manifests #1

New issue

Closed

opened 2026-03-01 22:10:38 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-03-01 22:10:38 +00:00

Contributor

Plan

plan-2026-02-25-mcp-gateway-migration — Phase 3 (pathfinder)

Repo

notion-mcp-remote — the repo where the code change happens

User Story

As a platform operator
I need Woodpecker CI pipeline and Kubernetes manifests for notion-mcp-remote
So that the service can be built, tested, and deployed automatically to the k8s cluster

Acceptance Criteria

When I push to main
Then Woodpecker runs ruff check/format and builds a container image to Harbor

When I apply the k8s manifests
Then the notion-mcp-remote service deploys with proper secrets, PVC, and monitoring

Additional Information

Phase 3 of the MCP gateway migration plan. This adds CI/CD and k8s infrastructure to the notion-mcp-remote repo following the established basketball-api pattern.

Deliverables:

.woodpecker.yaml with test (ruff) + kaniko build + Harbor push
k8s/ directory with deployment.yaml, service.yaml, pvc.yaml, servicemonitor.yaml, kustomization.yaml
ruff added to dev dependencies in pyproject.toml
Codebase formatted with ruff

Checklist

PR opened with related notes
Tests cover the acceptance criteria
Docs updated if needed

project-pal-e — the project this affects

### Plan `plan-2026-02-25-mcp-gateway-migration` — Phase 3 (pathfinder) ### Repo `notion-mcp-remote` — the repo where the code change happens ### User Story As a platform operator I need Woodpecker CI pipeline and Kubernetes manifests for notion-mcp-remote So that the service can be built, tested, and deployed automatically to the k8s cluster ### Acceptance Criteria When I push to main Then Woodpecker runs ruff check/format and builds a container image to Harbor When I apply the k8s manifests Then the notion-mcp-remote service deploys with proper secrets, PVC, and monitoring ### Additional Information Phase 3 of the MCP gateway migration plan. This adds CI/CD and k8s infrastructure to the notion-mcp-remote repo following the established basketball-api pattern. Deliverables: - `.woodpecker.yaml` with test (ruff) + kaniko build + Harbor push - `k8s/` directory with deployment.yaml, service.yaml, pvc.yaml, servicemonitor.yaml, kustomization.yaml - ruff added to dev dependencies in pyproject.toml - Codebase formatted with ruff ### Checklist - [ ] PR opened with related notes - [ ] Tests cover the acceptance criteria - [ ] Docs updated if needed ### Related - `project-pal-e` — the project this affects