Deploy evo-region per environment (ADR-0071): one replica with the Recreate strategy (a rolling update would deadlock on the lease), /readyz readiness, /livez liveness, no CPU limit and a drain inside the grace period, with the image digest doubling as the build identity. A new idempotent evo-world-clone provision subcommand creates genesis from development_opening (byte-identical to the qualification fixture) as a Sync hook after the migration. Dev and stage paths include their region; a dev AppProject allows Deployment and Service; region-drill.sh times rollout and forced-deletion recovery; the policy check enforces the host's invariants. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
17 lines
507 B
YAML
17 lines
507 B
YAML
# Operations endpoints (/livez, /readyz, /metrics) inside the cluster only; no
|
|
# NodePort or LoadBalancer (the quota forbids both). Scraping is enabled in M8.5.
|
|
apiVersion: v1
|
|
kind: Service
|
|
metadata:
|
|
name: evo-region-ops
|
|
annotations:
|
|
argocd.argoproj.io/sync-wave: "1" # After migration and provisioning.
|
|
labels:
|
|
app.kubernetes.io/name: evo-region
|
|
spec:
|
|
type: ClusterIP
|
|
selector:
|
|
app.kubernetes.io/name: evo-region
|
|
ports:
|
|
- {name: ops, port: 9100, targetPort: ops, protocol: TCP}
|