Register palinks in pal-e-services terraform #2

New issue

Closed

opened 2026-05-23 12:19:15 +00:00 by ldraney · 0 comments

ldraney commented

2026-05-23 12:19:15 +00:00

Owner

Type

Feature

Lineage

Standalone — containerization initiative for palinks.

Repo

ldraney/pal-e-services

User Story

As a platform operator
I want palinks registered in the services terraform
So that Harbor, ArgoCD, namespace, and funnel are provisioned automatically

Context

palinks currently runs as a local Puma process on archbox with an nginx reverse proxy in k3s. We're containerizing it to match the believers-elite pattern. This is the first step — terraform provisions all the infrastructure the other tickets depend on.

File Targets

Files the agent should modify or create:

terraform/k3s.tfvars — add palinks entry to services map

Files the agent should NOT touch:

terraform/main.tf — no module changes needed
terraform/cnpg.tf — CNPG cluster already exists

Acceptance Criteria

palinks entry added to k3s.tfvars services map (port 80, funnel true, source_path overlays/palinks/prod)
tofu apply succeeds without errors
Harbor project palinks exists with CI and pull robot accounts
ArgoCD application palinks created pointing at overlays/palinks/prod

Test Expectations

tofu plan shows only the expected new resources
tofu apply completes cleanly
Run command: cd ~/pal-e-services/terraform && tofu plan -var-file=k3s.tfvars

Constraints

Follow exact pattern from believers-elite entry in k3s.tfvars
Port 80 (Thruster wraps Puma)
funnel = true

Checklist

PR opened
tofu apply succeeds
No unrelated changes

palinks — project this affects

### Type Feature ### Lineage Standalone — containerization initiative for palinks. ### Repo `ldraney/pal-e-services` ### User Story As a platform operator I want palinks registered in the services terraform So that Harbor, ArgoCD, namespace, and funnel are provisioned automatically ### Context palinks currently runs as a local Puma process on archbox with an nginx reverse proxy in k3s. We're containerizing it to match the believers-elite pattern. This is the first step — terraform provisions all the infrastructure the other tickets depend on. ### File Targets Files the agent should modify or create: - `terraform/k3s.tfvars` — add `palinks` entry to `services` map Files the agent should NOT touch: - `terraform/main.tf` — no module changes needed - `terraform/cnpg.tf` — CNPG cluster already exists ### Acceptance Criteria - [ ] `palinks` entry added to `k3s.tfvars` services map (port 80, funnel true, source_path overlays/palinks/prod) - [ ] `tofu apply` succeeds without errors - [ ] Harbor project `palinks` exists with CI and pull robot accounts - [ ] ArgoCD application `palinks` created pointing at `overlays/palinks/prod` ### Test Expectations - [ ] `tofu plan` shows only the expected new resources - [ ] `tofu apply` completes cleanly - Run command: `cd ~/pal-e-services/terraform && tofu plan -var-file=k3s.tfvars` ### Constraints - Follow exact pattern from believers-elite entry in k3s.tfvars - Port 80 (Thruster wraps Puma) - funnel = true ### Checklist - [ ] PR opened - [ ] tofu apply succeeds - [ ] No unrelated changes ### Related - `palinks` — project this affects