# The deployment-local overlay: the two things that differ per deployment — the domain and the
# bootstrap administrator — are set here and nowhere else. It overrides incluster.yaml,
# dockerhub.yaml, and the chart defaults.
#
#   cp deploy/values/domain.example.yaml deploy/values/domain.yaml   # then fill in the real values
#   make deploy-incluster   # applies domain.yaml with -f when it exists; so does make prod-deploy
#
# The real file (domain.yaml) is git-ignored; only this example is tracked.
global:
  domains:
    console: gshare.example.com   # replace with the real domain; the console, the sessions at
                                  # /proxy/{cr}, and the ingress host all follow this one value

# The super_admin account created on first start. The display name is edited from the console.
bootstrapAdmin:
  email: admin@example.com        # the administrator's real email, which is the login id
  password: "12345678"    # initial password, forced to change at first login;
                                  # set to "" to have one generated

# ── Optional per-deployment knobs (all have working chart defaults) ─────────────────────────────
# Sessions are linked with https URLs by default; a plain-HTTP LAN deployment (no TLS proxy)
# sets this so the connect buttons work:
#   sessionUrlScheme: http     # (under global:)

# Pin the whole control plane (api, worker, frontend, data tier) and the operator to one node,
# so GPU and CPU workers carry only sessions:
# controlPlane:
#   nodeSelector: { "kubernetes.io/hostname": my-master }

# operator:
#   nodeSelector: { "kubernetes.io/hostname": my-master }
#   # MIXED GPU FLEET (different models in one cluster): pin each session pod to the exact card
#   # the ledger reserved (nvidia.com/use-gpuuuid). Without it hami-scheduler may place a session
#   # priced for one model onto another. Single-model fleets can leave it off.
#   perCardMode: true
#   # Volumes with real quotas (the optional ZFS/democratic-csi storage node):
#   volumeStorageClass: gshare-data
#   # Idle-reaper utilization source. Prefer Prometheus (deploy/monitoring/monitoring-stack.yaml):
#   # the HAMi monitor URL is a Service that round-robins per-node pods, which mis-reads other
#   # nodes' cards as busy on multi-GPU-node clusters (idle sessions then never auto-pause).
#   prometheusUrl: http://prometheus.monitoring.svc:9090

# Admin image-build pipeline (console "build image") pushes here; also where locally built
# session images live when you run the LAN registry (deploy/registry/registry.yaml):
# api:
#   buildRegistry: "<storage-node-ip>:5000/gshare-user"