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>
25 lines
954 B
YAML
25 lines
954 B
YAML
# Watches ./dev/api-gateway so the entrypoints in it — the GitRepository above,
|
|
# the gateway and policies Kustomizations, the ExternalSecrets — reconcile from
|
|
# git instead of waiting on a kubectl apply. Lives in that directory, so it
|
|
# manages itself.
|
|
#
|
|
# In the workforce namespace, not flux-system. The gateway Kustomizations sat in
|
|
# flux-system only because postBuild.substituteFrom reads a ConfigMap from its
|
|
# own namespace and dataplane-template-defaults existed nowhere else. That
|
|
# ConfigMap is now in every domain namespace, so the constraint is gone and the
|
|
# team can own its own gateway.
|
|
#
|
|
# Apply once with kubectl. That is the last manual apply this repo needs.
|
|
apiVersion: kustomize.toolkit.fluxcd.io/v1
|
|
kind: Kustomization
|
|
metadata:
|
|
name: dataplane-workforce-dev-bootstrap
|
|
namespace: workforce
|
|
spec:
|
|
interval: 10m
|
|
sourceRef:
|
|
kind: GitRepository
|
|
name: dataplane-workforce-dev
|
|
path: ./dev/api-gateway
|
|
prune: true
|