pal-e-docs

Phase 1: Service Onboarding

phase-mcd-tracker-1-service-onboarding Phase

phase
Project
Goal: Production namespace, Harbor project, ArgoCD app, and kustomize overlay ready — before any code exists.
Owner: Dev agent
Repo: forgejo_admin/pal-e-services, forgejo_admin/pal-e-deployments
Depends on: None

Follow service-onboarding-sop and convention-kustomize-overlay to onboard mcd-tracker as a new service on the platform. This is pure infrastructure — no application code.
  • Add mcd-tracker entry to pal-e-services/terraform/k3s.tfvars var.services map: 
    mcd-tracker = {
  forgejo_repo = "forgejo_admin/mcd-tracker-api"
  image_repo   = "mcd-tracker/api"
  port         = 8000
  funnel       = true
  source_repo  = "forgejo_admin/pal-e-deployments"
  source_path  = "overlays/mcd-tracker/prod"
}
  • tofu plan -lock=false → verify 6-7 new resources (namespace, Harbor project, robot accounts, pull secret, ArgoCD app, funnel ingress)
  • tofu apply -lock=false
  • Create kustomize overlay: pal-e-deployments/overlays/mcd-tracker/prod/

Architecture Touch

arch-deployment-mcd-tracker — this phase creates the infrastructure depicted in the deployment diagram. No diagram update needed (diagram was written with this phase in mind).

Verification

  • kubectl get ns mcd-tracker — namespace exists
  • ArgoCD app mcd-tracker visible in ArgoCD UI (will be degraded/missing until first image push — expected)
  • Harbor project mcd-tracker exists with CI + pull robot accounts
  • Kustomize overlay renders: kubectl kustomize pal-e-deployments/overlays/mcd-tracker/prod/

  • pending
  • plan-mcd-tracker — parent plan
  • service-onboarding-sop — procedure
  • convention-kustomize-overlay — overlay pattern
  • arch-deployment-mcd-tracker — deployment diagram