Stéphane Tailland
023a89bf71
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>
19 lines
754 B
YAML
19 lines
754 B
YAML
# HTTPS with no credentials, unlike the platform repos which use SSH and a
|
|
# deploy key from Vault. Deliberate: this repo is already anonymously readable over
|
|
# HTTPS on gitea, so a deploy key would guard nothing while adding a Vault entry
|
|
# and a gitea key to create by hand before anything deploys. TLS still gives
|
|
# integrity and authenticity of the source.
|
|
#
|
|
# If the gitea repos are ever made private, this becomes an SSH sourceRef with
|
|
# an ExternalSecret holding the deploy key — the pattern the platform repos use.
|
|
apiVersion: source.toolkit.fluxcd.io/v1
|
|
kind: GitRepository
|
|
metadata:
|
|
name: catalogue-agent
|
|
namespace: agents
|
|
spec:
|
|
interval: 5m
|
|
url: https://gitea.sttlab.eu/stt/classic-models-agent-catalogue.git
|
|
ref:
|
|
branch: main
|