Files
classic-models-agent-catalogue/dev/bootstrap-kustomization.yaml
T
Stéphane Tailland 58325b470a Name the Kubernetes objects in English
catalogue-agent and approvisionnement-agent named a Deployment, a Service, an
Ingress and a Certificate in French, in an estate where nothing else is.

The peer URLs move with them, set through the existing per-environment override
so the rename takes effect without rebuilding an image; the defaults in the code
carry the same values for the next build.

The Keycloak client ids, the image names and the repository names are still
French. They are a separate, heavier move.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-31 09:12:46 +02:00

34 lines
1.3 KiB
YAML

# Watches ./dev, so the GitRepository and the Kustomization below it reconcile
# from git like any other manifest. It lives in ./dev itself, so it also manages
# itself — the arrangement `flux bootstrap` sets up, which flux-operator does
# not create, and the same one the platform repos use.
#
# It sits in the agents namespace, not flux-system: a sourceRef resolves in the
# Kustomization's own namespace, and this is the agent team's to own.
#
# Three manual applies, once, to close the loop — nothing can watch ./dev until
# the namespace and the source that serves it exist:
#
# kubectl apply -f k8s/namespace.yaml
# kubectl apply -f dev/gitrepository.yaml
# kubectl apply -f dev/bootstrap-kustomization.yaml
#
# After that every file in this repo, this one included, reconciles from git.
#
# Sharp edge: with prune enabled, deleting flux-kustomization.yaml from git
# deletes the Kustomization it defines, and that Kustomization's own prune then
# removes the whole deployment. Correct GitOps behaviour, blast radius two
# levels deep.
apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata:
name: catalog-agent-bootstrap
namespace: agents
spec:
interval: 10m
sourceRef:
kind: GitRepository
name: catalog-agent
path: ./dev
prune: true