Files
aevolution/deploy/kubernetes/region/dev/kustomization.yaml
T
dingoandClaude Opus 5.5 b923ce1721 deploy(dev): serve a cellular region 100/2 for the M11.3 probe
Region 100/1 holds lineage history and cannot host the cellular profile,
so dev provisions a fresh cellular-v1 genesis at region 2 and serves it
with --profile cellular and its --life-route catalog. Region 1's stores
are left untouched; it is no longer served.

The base Deployment and provision Job take REGION_PROFILE,
REGION_LIFE_ROUTES, REGION_OPENING and REGION_OPENING_ARGS. Their
defaults keep stage on the lineage profile with the development opening.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 10:23:52 -04:00

17 lines
640 B
YAML

# Region host for evolution-dev: world 100, region 2, frame 9 (cellular-v1 opening, M11.3).
# The server image digest appears twice on purpose: as the image and as the build
# identity the region records in every commit. The policy check requires they match.
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: evolution-dev
resources:
- ../base
components:
- ../dev-session-route
images:
- name: aevolution-server
newName: registry.aeternalisgames.com/aeternalis/aevolution-server
digest: sha256:566c29329433934f1436faf94652a7b925df8b4587ab04470322172f47c31c02
patches:
- path: region-values.yaml