arbi-serve {{ .Chart.Version }} installed as {{ include "arbi-serve.fullname" . }} (one engine pod{{ if .Values.gpu.count }}, {{ .Values.gpu.count }} GPU{{ end }}).
{{- if eq .Values.exposure.mode "sharedGate" }}

API (the gate; every route needs a customer key whose SHA-256 is in the Secret "{{ include "arbi-serve.keysSecret" . }}", key keys.sha256):
  kubectl -n {{ .Release.Namespace }} port-forward svc/{{ include "arbi-serve.fullname" . }} 8000:{{ .Values.service.port }}
  curl -s localhost:8000/health/ready -o /dev/null -w '%{http_code}\n'      # 200 once the engine is ready

Secrets this release expects (create them out of band, see k8s/README.md):
  {{ include "arbi-serve.authSecret" . }}   keys: tokens, internal_token
  {{ include "arbi-serve.keysSecret" . }}   key:  keys.sha256   (optional: without it every request is 401)
{{- else }}

Shared engine (exposure.mode=tenantGates): Service {{ include "arbi-serve.fullname" . }}:{{ .Values.engine.port }}, reachable only through tenant gates.
Each tenant release (chart arbi-serve-tenant) adds its own NetworkPolicy allow-<tenant-namespace> here; deleting it revokes that tenant.

Secret this release expects (create it out of band, see k8s/README.md):
  {{ include "arbi-serve.authSecret" . }}   keys: tokens, internal_token
{{- end }}
{{- if eq .Values.cache.shared.mode "overlay" }}

NOTE: cache.shared.mode=overlay runs a PRIVILEGED init container (the namespace needs Pod Security `privileged`) and is not validated on a real node.
{{- end }}
