Files
classic-models-agent-catalogue/k8s/deployment.yaml
T
Stéphane Tailland 023a89bf71 Rename back to catalogue-agent; stop owning the shared namespace
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>
2026-08-31 15:12:25 +02:00

77 lines
2.5 KiB
YAML

apiVersion: apps/v1
kind: Deployment
metadata:
name: catalogue-agent
namespace: agents
spec:
# One replica, and that is a constraint rather than a default. Conversation
# history — which the confirm-before-writing flow depends on — lives in the
# process, keyed by A2A contextId. A second replica would route the user's
# "yes" to a pod that never saw the question. Scaling out needs sticky routing
# on contextId or a shared store first.
replicas: 1
selector:
matchLabels:
app: catalogue-agent
template:
metadata:
labels:
app: catalogue-agent
spec:
securityContext:
runAsNonRoot: true
runAsUser: 10001
seccompProfile:
type: RuntimeDefault
containers:
- name: agent
# gitea's own registry, not ghcr: the image sits beside the source it
# was built from, and the package inherits the repo's visibility. The
# repo is public, so the pull needs no credentials — which removes an
# imagePullSecret that would otherwise have to be created by hand in
# this namespace and kept in step with a GitHub token.
image: gitea.sttlab.eu/stt/classic-models-agent-catalogue:v0.4.0
ports:
- name: http
containerPort: 8080
envFrom:
- configMapRef:
name: catalogue-agent-config
- secretRef:
name: catalogue-agent-secrets
volumeMounts:
- name: sttlab-ca
mountPath: /etc/sttlab-ca
readOnly: true
# The Agent Card needs no auth and is served by the same app, so a 200
# means the A2A routes are genuinely mounted — not merely that the
# process is alive.
readinessProbe:
httpGet:
path: /.well-known/agent-card.json
port: http
initialDelaySeconds: 5
periodSeconds: 10
livenessProbe:
httpGet:
path: /.well-known/agent-card.json
port: http
initialDelaySeconds: 15
periodSeconds: 20
resources:
requests:
cpu: 50m
memory: 192Mi
limits:
cpu: "1"
memory: 512Mi
securityContext:
allowPrivilegeEscalation: false
readOnlyRootFilesystem: true
capabilities:
drop: ["ALL"]
volumes:
- name: sttlab-ca
configMap:
name: sttlab-ca