Stéphane Tailland
3c5025ee52
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 to catalog. The id no longer transits a shared namespace either, which was a compromise this repo documented rather than liked. Adds the GitRepository this repo never had — its Kustomizations point at k8s-platform for templates, and nothing needed to read the repo that declares them, because those declarations were applied by hand. It reuses the domain's existing deploy key rather than minting one; verified that the key reads this repository. Worth knowing what that implies: the key is not scoped to a single repo, so the isolation its per-repo name suggests does not exist. And the bootstrap Kustomization that watches ./dev/api-gateway, so all of it reconciles from git from now on. Migration is not a patch: a namespace is immutable, so the existing objects have to be deleted and recreated. Deleting a Kustomization with prune enabled would take its Gateway, GatewayConfiguration and mirror CR with it, so prune has to be turned off on the old objects first, then the new ones adopt what is already running. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
dataplane-catalog
Layer 2 (Gateway infrastructure) for the catalog bounded context
(domain team: catalog) — one Control Plane per environment, referenced by
ID (created by ../konnect-platform, never recreated here).
This repo does NOT hold KonnectAPIAuthConfiguration/GatewayConfiguration/
Gateway/Certificate YAML directly. The actual resource template (one
copy, covering every domain/environment) lives in
../k8s-platform/dataplane-template/, ${VAR}-parameterized. This repo
only holds what's specific to one <env>/<gateway-type>/ — two files:
kustomization.yaml— a FluxKustomizationCR (not a plain Kustomize build file, despite the name) that builds../k8s-platform/dataplane-template/from thek8s-platformGitRepositorysource. Domain-specific non-sensitive values (NAME,NAMESPACE,CONTROL_PLANE_ID,HOSTNAME,TLS_ISSUER_NAME) are inline underspec.postBuild.substitute— no separate ConfigMap to forget to re-apply after an edit (bit us twice before this got simplified). Cluster-wide defaults (KONNECT_SERVER_URL,GATEWAY_IMAGE,REPLICAS,TLS_ISSUER_KIND) come fromdataplane-template-defaults, a ConfigMap shared by every domain, viasubstituteFrom.externalsecret.yaml— anExternalSecret(External Secrets Operator) that pulls the Konnect PAT from Vault (secrets/kong-v2/catalog/dev/konnect-patathttps://vault.sttlab.eu, via the sharedClusterSecretStore vault-kong-v2) and materializes it directly ascatalog-dev-konnect-authin thecatalognamespace. Not part of the substitute/substituteFrom flow above — Flux's substitution would have required the real PAT to sit in a Secret influx-system(shared, broadly-readable namespace) before landing here, which was rejected. Rotation is now just "update the value in Vault" —ExternalSecret'srefreshInterval(1h) picks it up automatically, nothing to touch in the cluster or in git.