Stéphane Tailland
2acb2d56ec
The gateway and policies Kustomizations sat in flux-system, and so did the Secret carrying the control-plane id. Neither was a governance decision: postBuild.substituteFrom resolves only in the Kustomization's own namespace, dataplane-template-defaults existed only in flux-system, so everything that needed it had to live there too — in a namespace the feature team has no access to. The team could not touch its own gateway. k8s-platform now places that ConfigMap in every domain namespace, so the constraint is gone. Move both Kustomizations and the control-plane ExternalSecret into the domain namespace; the id no longer transits a shared namespace either. sourceRef gets an explicit namespace: flux-system, because it resolves in the Kustomization's own namespace and k8s-platform is not there. Naming it beats duplicating the source per domain, and the split is the point — templates belong to the platform, the Kustomization consuming them belongs to the team. Verified on catalog first: without this the moved objects report "GitRepository k8s-platform not found". Adds the GitRepository this repo never had, reusing the domain's existing deploy key; that key was verified to read the dataplane repositories, which also means it is not scoped to one repo. And the bootstrap Kustomization watching ./dev/api-gateway, so all of it reconciles from git from now on. Migration is not a patch: a namespace is immutable, so these objects are deleted and recreated. Deleting a Kustomization with prune enabled would take its Gateway, GatewayConfiguration and mirror CR with it, so prune is turned off on the old objects first and the new ones adopt what is already running. Done that way on catalog with no pod restart and no Kong entity lost. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
dataplane-workforce
Layer 2 (Gateway infrastructure) for the workforce bounded context
(domain team: workforce) — one Control Plane per environment, referenced
by ID (created manually in Konnect for now, never recreated here:
1dbd741c-0da2-4718-8c72-6f479530b371 for dev).
Same gateway-kustomization.yaml / externalsecret.yaml /
policies-kustomization.yaml three-file pattern as dataplane-catalog/
dataplane-customers/dataplane-payments/dataplane-sales — see
dataplane-catalog/README.md for the full explanation of each file's
role, identical here, not repeated.
IdP: https://keycloak.sttlab.local/realms/classic-models (local
in-cluster Keycloak), platform-wide default — see ../STATUS.md sections
15/16. JWT_AUDIENCE_WHITELIST set to ["workforce-api", "mcp-workforce"]
from the start — Layer 3 (REST + MCP) was built the same session, see
../STATUS.md section 23.
Only dev/ is real. staging/api-gateway/ and prod/api-gateway/
still hold the original TODO placeholder files, not converted, not
deployed.
Layer 3 is real here too: ../workforce-api (REST + MCP over Office
and Employee) was built and deployed the same session — Gateway workforce-dev: Programmed: True, DNS entry added to coredns-custom
(workforce-dev.sttlab.local → the dataplane-ingress-workforce-dev-*
Service ClusterIP, same manual per-domain step documented in
../STATUS.md section 17), all routes smoke-tested (401, not
404/502).
Self-service pipeline (../konnect-platform generating this content
automatically) does not exist yet — still a stub per ../STATUS.md.
Everything here is hand-maintained.