The chart's first green install-test leg took 2m35s including cluster
creation (Gitea PR #61), against an estimate of roughly five minutes for the
pull alone. Recorded in both places the estimate had been reasoned about.
The general point belongs on the CI-CD page rather than only on the chart
page: a large image moves the all-charts figure less than it looks, because
the legs run concurrently and that figure tracks the slowest leg plus
scheduling, never the sum of the pulls.
convertx: new chart page, index row, sidebar entry, two lessons
The chart page follows outline.md: prerequisites, installation walkthrough,
the required 1Password field, the complete values reference and the operating
notes. No version rows, as on every chart page.
The notes it carries are the ones that cannot be read off the values:
- the chart bypasses the image entrypoint, which is what keeps the hardening
baseline intact on an image that carries no USER - together with the
obligation that creates, namely re-reading the upstream entrypoint at every
app-version bump
- uid 1000 rather than the repo's 20000, because the image owns /home/convertx
with it and the uid owns data on a PersistentVolume
- what has to be writable and why: /home/convertx is HOME, and LibreOffice is
invoked without -env:UserInstallation, so its profile can only go there
- the probes use /healthcheck; "/" is never a 200
- whoever opens the page first becomes the administrator, and
accountRegistration does not gate that
- the ingress annotation is the only upload ceiling, because the application
enforces none
- WEBROOT, PUID/PGID/UMASK and PORT do not belong in the env block
Two entries in Lessons learned, both preventive rather than post-mortem, in
the shape the valkey entries already use:
- the probe that would have passed on a redirect and meant something else a
week later - a 3xx makes an httpGet pass, so a redirecting path hides the
question instead of answering it, and the answer has to hold for every
state the application can be in
- the entrypoint we skipped, and the obligation that created - an override
forks the entrypoint silently, and a fork with no diff is a fork nobody
reviews, so the warning belongs at the line the next change will touch
Also corrected in CI-CD: the per-chart publish workflow count, which read 24
and was already one behind before this chart made it 26.
jklein