#310: Ingress + HTTPRoute + scheduling knobs, env-driven admin, listen wiring #425
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "mf-310"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Manuel's findings. Chart 0.4.0:
ingress.*(className/annotations/hosts/tls) andhttpRoute.*(parentRefs/hostnames) templates, bothenabled-gated and default-off, routing only to Cairn (never the converter);nodeSelector/tolerations/affinityfor the Cairn pod and the converter pod;listen.portsetsCAIRN_LISTENon the pod and drives the containerPort — single source of truth, the config Secret needs nolisten. Go:applyAdminEnv(CAIRN_ADMIN_USERNAME+CAIRN_ADMIN_PASSWORD_HASHpreferred / plaintextCAIRN_ADMIN_PASSWORDhashed at boot with loud warning), upserts the user + grants admin immediately after config load so first-run never triggers; half-configured or non-PHC hash refuses boot; tested (upsert, verify, replace-in-place, refusals). admin/admin-in-image declined as superseded by setup mode. Docs + CHANGELOG v0.6.127. Part of #310.