Rename back to catalogue-agent; stop owning the shared namespace

catalog-agent was one rename too aggressive: 'catalogue' is accepted, and the
Keycloak client, its audience scope and the Vault key that names it were never
renamed to match — leaving an inconsistency between what Kubernetes and
Keycloak call the same agent. Keycloak carries more weight to move, so this
side moves back.

k8s/namespace.yaml is out of this Kustomization's inventory. It was in
2026-08-31 when renaming the Kustomization pruned the old one — which owned
the namespace three agents share — and took all three down. A namespace shared
across repos should not be owned by any one of them.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

This commit is contained in:

Stéphane Tailland

2026-08-31 15:12:25 +02:00

parent 9b713a894c

commit 023a89bf71

11 changed files with 34 additions and 27 deletions

									
										k8s/kustomization.yaml
									
		-1
	
												View File
												
				@@ -1,7 +1,6 @@

				apiVersion: kustomize.config.k8s.io/v1beta1

				kind: Kustomization

				resources:

				  - namespace.yaml

				  - ca-configmap.yaml

				  - externalsecret.yaml

				  - configmap.yaml