Repository navigation
Carry BRANDING from the MINT chart to the pod at TACC #207
Description
Part of #79.
Question
Carry BRANDING from the MINT chart to the pod at mint.tacc.utexas.edu.
#206 adds the key to ui-react. That alone changes nothing in production.
#204 measured why: the chart builds the
ui_react ConfigMap from a hardcoded list of ten keys, and it has no extraEnv escape hatch.
An operator cannot add a variable.
This is the #150 failure mode. There, the image held a compiled-in default, the chart never sent
the key, and no values file could override it.
Work
1. mintproject/mint — external repository, chart 9.0.0-beta.10 at 28fedea.
Add to charts/mint/templates/ui-react-config.yaml, beside the other optional keys:
{{- with $cfg.branding }}
BRANDING: {{ . | quote }}
{{- end }}Add branding: "" under components.ui_react.config in charts/mint/values.yaml.
Add the row to charts/mint/README.md. Bump the chart version.
2. dynamo — private repository.
Set the value and the new chart version:
components:
ui_react:
config:
branding: taccDecision
Use components.ui_react.config.branding, not a top-level key.
The chart forwards two optional keys by two different routes. EXECUTION_ENGINE uses
$cfg.execution_engine under the component. WELCOME_MESSAGE reads top-level
.Values.welcome_message, which it shares with the legacy UI. Follow EXECUTION_ENGINE.
#81 retires the legacy UI, so a shared key buys nothing.
Acceptance
kubectl exec into the ui_react pod at TACC. Read env-config.js in the nginx web root.
It must contain BRANDING: "tacc". A green helm upgrade is not proof.
Activity
mosoriob commentedon Sep 1, 2026
dynamois readable after all. It is cloned locally at/Users/mosorio/repos/github.com/In-For-Disaster-Analytics/dynamo. The remote org isIn-For-Disaster-Analytics, notmintproject, which is why#204 reported it unreadable.
Three facts change this ticket.
1. TACC already pins the current chart.
shared/Chart.yaml:9pins MINT9.0.0-beta.10,which is the latest published version. So step 2 needs a new chart release; there is no
older version to catch up to first.
2.
ui_reactis switched off at TACC.shared/values.yaml:107-111:Its own comment says TACC still serves the legacy
uionmint.tacc.utexas.edu, and thatturning it on is #81.
So the values block has no
config:key at all. Addingbrandingmeans creating the block:enabled: truebelongs to #77 and#81, not here. Coordinate, or the two
tickets will edit the same five lines.
3. The checkout sits on an unmerged branch,
chore/mint-beta.10-global-imagetag. Checkwhich branch carries the beta.10 pin before you edit, and see
one-image-tag-names-the-system: a per-serviceimage.tagsilently beatsglobal.imageTag.The acceptance check is unchanged. Read
env-config.jsinside the running pod.mosoriob commentedon Sep 12, 2026
Both halves are built, merged and published. The key reaches a browser. The acceptance
check cannot run at TACC yet, and that is structural — it is #77's work, not a gap here.
What shipped
Chart —
mintproject/mint, PRs #114 and #115.ui-react-config.yamlforwardsBRANDINGfrom$cfg.branding, beside the other optional keys, exactly asEXECUTION_ENGINEdoes.branding: ""is added undercomponents.ui_react.configinvalues.yaml, with the README row. Released and published as9.0.0-beta.11, confirmedby unpacking
MINT-9.0.0-beta.11.tgzfromhttps://mintproject.github.io/mint/, not byreading the working tree.
Values —
dynamo, PR #15, merged tomainas85149e7. It setsbranding: taccundercomponents.ui_react.configand moves the chart pin from9.0.0-beta.10to9.0.0-beta.11.enabled: falseis untouched, so the two tickets did not collide on the same five lines.9.0.0-beta.12is on the chart'smainbut is not published. It adds a Hasura PVC fix and acomment move. Nothing here needs it.
Verified, not assumed
The whole chain runs on the dev cluster. It is at
MINT-9.0.0-beta.11, revision 71, withcomponents.ui_react.config.branding: taccin its own values — the same key path TACC uses.kubectl get configmap mint-ui-react-config-map→"BRANDING":"tacc".kubectl exec deploy/mint-ui-react -- cat /usr/share/nginx/html/env-config.js→"BRANDING": "tacc".That clears the second blocker #204 named.
generate-env-config.mjscopies only namedkeys through
pick(), so an unknown variable is dropped even when the pod carries it. #206added the key to the generator, and this measures it in a running pod. The image also carries
tacc-white.pngandutaustin-white.pngunder/usr/share/nginx/html/images/.TACC's own values render the key.
helm templateondynamo/sharedwithui_react.enabled=truegivesBRANDING: "tacc", beside TACC's real Hasura, CKAN andEnsemble Manager hosts.
Why the acceptance check moves to #77
The check reads
env-config.jsinside theui_reactpod at TACC. There is no such pod:enabled: false, and turning it on is #77 and #81. So #207 blocks #77 while its ownacceptance needs #77 — a circle. TACC's cluster is also driven from
login-shared.tacc.utexas.edu, which needssshand MFA.Break the circle here. This ticket closes on the render proof. The in-pod read lands on
#77 as a constraint, beside the habit the
map already keeps: read the served
env-config.jsat the real host before believing the flip.Two facts for #77, and the map's "one line" is wrong
The render with
enabled: truealone is not deployable. Two values are still missing.AUTH_CLIENT_IDrenders"mint-local", the chart default from62d9ef3. TACC needs"mint"— see #73.ui_reactingress takes the chart default hostmint.local, with no TLS, whileLit keeps
mint.tacc.utexas.eduand theminttaccsecret.So the flip is a four-part values block, not one line:
enabled: true,client_id: "mint",the ingress host, and the
minttaccTLS secret — and Lit's own ingress must move aside in thesame edit. #150 recorded "one line,
client_id: mint". That reading is now measured and it is wrong.mosoriob commentedon Sep 12, 2026
Closed on the render proof. The in-pod read at TACC moves to #77.