GitOps Deploy via pal-e Platform

story-notion-mcp-remote-ops-deploy-gitops User Story

active user-story

Project

story: GitOps Deploy via pal-e Platform

Role

Operator — responsible for keeping notion-mcp-remote running, observable, and SOP-compliant inside the pal-e cluster.

Key

ops-deploy-gitops

Want

As an operator, I want notion-mcp-remote to deploy via the standard pal-e pipeline (Woodpecker → Harbor → ArgoCD) with health + metrics endpoints wired to ServiceMonitor.

So That

So that the service meets service-onboarding-sop, is visible in the platform's observability stack, and has zero bespoke deploy paths to maintain.

Acceptance Criteria

[ ] Woodpecker pipeline builds on push to main, pushes to internal Harbor URL
[ ] pal-e-services var.services entry landed via PR
[ ] pal-e-deployments kustomize overlay landed via PR
[ ] tofu apply creates namespace, ArgoCD Application, Harbor project + robots, Tailscale Funnel ingress
[ ] Secrets provisioned via kubectl create secret generic before first ArgoCD sync
[ ] ArgoCD reports Application healthy and synced
[ ] ServiceMonitor scrapes /metrics and Prometheus sees notion_mcp_remote_up 1

Success Metric

pre-deploy-validation checklist from service-onboarding-sop is 100% green before first apply. Zero manual kubectl edits post-deploy.

arch-deployment-notion-mcp-remote

project-notion-mcp-remote
board-notion-mcp-remote
service-onboarding-sop