Namespace rename — pal-e-docs-app to pal-e-app in k8s and ArgoCD #257

New issue

Closed

opened 2026-03-30 22:10:10 +00:00 by forgejo_admin · 1 comment

forgejo_admin commented

2026-03-30 22:10:10 +00:00

Contributor

Type

Feature

Lineage

Depends on Keycloak client rename (#255).

Repo

forgejo_admin/pal-e-platform

User Story

As a stakeholder
I want to access pal-e-app at a clean URL
So that the deployment name matches the project identity

Context

The pal-e-app frontend is currently deployed in namespace pal-e-docs-app with Tailscale funnel hostname pal-e-docs-app.tail5b443a.ts.net. This needs to become pal-e-app namespace with pal-e-app.tail5b443a.ts.net hostname. Requires coordination across pal-e-deployments (kustomize overlay), pal-e-services (ArgoCD Application), and Tailscale Ingress.

File Targets

Files to modify:

pal-e-deployments — rename or create pal-e-app overlay
pal-e-services — update ArgoCD Application if applicable
Tailscale Ingress — new funnel hostname

Files NOT to touch:

pal-e-docs API namespace — stays as pal-e-docs

Acceptance Criteria

pal-e-app pod runs in pal-e-app namespace
Tailscale funnel at pal-e-app.tail5b443a.ts.net serves the frontend
Old pal-e-docs-app namespace and funnel cleaned up
ArgoCD syncs the new deployment

Test Expectations

Manual: app accessible at new URL
Manual: Keycloak login redirect works with new URL

Constraints

Coordinate with Keycloak client rename (#255)
Use tofu plan -lock=false for any terraform changes

Checklist

PR opened
Tests pass
No unrelated changes

project-pal-e-app
arch-deployment-pal-e-app

### Type Feature ### Lineage Depends on Keycloak client rename (#255). ### Repo `forgejo_admin/pal-e-platform` ### User Story As a stakeholder I want to access pal-e-app at a clean URL So that the deployment name matches the project identity ### Context The pal-e-app frontend is currently deployed in namespace pal-e-docs-app with Tailscale funnel hostname pal-e-docs-app.tail5b443a.ts.net. This needs to become pal-e-app namespace with pal-e-app.tail5b443a.ts.net hostname. Requires coordination across pal-e-deployments (kustomize overlay), pal-e-services (ArgoCD Application), and Tailscale Ingress. ### File Targets Files to modify: - `pal-e-deployments` — rename or create pal-e-app overlay - `pal-e-services` — update ArgoCD Application if applicable - Tailscale Ingress — new funnel hostname Files NOT to touch: - pal-e-docs API namespace — stays as pal-e-docs ### Acceptance Criteria - [ ] pal-e-app pod runs in pal-e-app namespace - [ ] Tailscale funnel at pal-e-app.tail5b443a.ts.net serves the frontend - [ ] Old pal-e-docs-app namespace and funnel cleaned up - [ ] ArgoCD syncs the new deployment ### Test Expectations - [ ] Manual: app accessible at new URL - [ ] Manual: Keycloak login redirect works with new URL ### Constraints - Coordinate with Keycloak client rename (#255) - Use tofu plan -lock=false for any terraform changes ### Checklist - [ ] PR opened - [ ] Tests pass - [ ] No unrelated changes ### Related - `project-pal-e-app` - `arch-deployment-pal-e-app`

forgejo_admin referenced this issue

2026-04-11 20:43:07 +00:00

Close stale pal-e-app / pal-e-docs-app rename tickets after pal-e-production landing #279

forgejo_admin referenced this issue

2026-04-11 20:57:21 +00:00

Close stale pal-e-app / pal-e-docs-app rename tickets after pal-e-production landing #279

forgejo_admin commented

2026-04-12 15:37:59 +00:00

Author

Contributor

Closing — pal-e-docs-app and pal-e-app names are obsolete; canonical namespace is pal-e-production. Forward-facing Keycloak client rename deferred under forgejo_admin/pal-e-platform#278.

Closing — `pal-e-docs-app` and `pal-e-app` names are obsolete; canonical namespace is `pal-e-production`. Forward-facing Keycloak client rename deferred under forgejo_admin/pal-e-platform#278.

forgejo_admin closed this issue

2026-04-12 15:37:59 +00:00