Helm falls back to the "default" namespace when --namespace is omitted, so a
forgotten flag (or a Kustomize helmCharts entry without namespace) silently
deployed into the wrong place. Render the namespace through one helper that
fails on an empty or implicit "default" namespace, with allowDefaultNamespace
as an explicit opt-in.
scripts/check-chart.sh lints the chart, asserts every namespaced resource
carries the passed namespace, and checks both failure and opt-in paths. CI runs
it instead of the plain template call.
Bump the chart to 0.2.1.
Replace the OCI chart push with a classic Helm repository in the public
TapTap/Charts repository. CI packages the chart, regenerates index.yaml and
pushes both to main, so `helm repo add` and Kustomize helmCharts work.
The publisher authenticates with the AUDIOMANAGER_CHARTS_TOKEN secret and
supports an explicit VERSION for local releases.
Use the product and image name for the chart, release, namespace, secrets,
container and rendered file paths. The application package and local config
paths keep their existing names.
Bump the chart to 0.1.2 so the new chart name and paths are a distinct
release. CI now publishes oci://gitea.tap-tap.win/taptap/charts/audiomanager.
Add a chart-push job that runs after the chart lint on every push and
publishes the packaged chart to oci://gitea.tap-tap.win/taptap/charts.
Main builds use <chart version>-sha.<commit> so parallel commits do not
overwrite each other; v* tags use the tag version. The shared
scripts/push-chart.sh also supports explicit VERSION and local use.
Kaniko unpacks the final stage over /, so tools from the CI image (node in
particular) are gone after the build. The checkout action's post step then
fails with exit code 127 even though the image was pushed successfully.
Use a plain git fetch/checkout in the image job, which has no JavaScript action
and therefore no post step.
A multi-stage kaniko build replaces / with the last stage's root filesystem,
which deletes $HOME/.docker/config.json. Kaniko then resolves credentials at
push time without them, asks the registry for an anonymous token and Gitea
rejects the upload with 401 reqPackageAccess.
Keep the Docker credential store in /kaniko/.docker for the whole image job via
DOCKER_CONFIG and let docker login write there directly. Restore the image job
and document that CI publishes images again.
The Gitea registry rejects kaniko pushes from job containers with
401 reqPackageAccess even though the same credentials work from a normal
machine, so the image job could never go green.
Drop the image job; CI now only runs unit tests, the smoke test and the
Helm chart lint. Add scripts/release.sh, which builds and pushes the
image from a trusted machine and can optionally apply the users secret
and run helm upgrade.
The runner does not expose its Docker socket to job containers, so the
image job could not run docker build. Include the kaniko executor in the
CI image and build/push directly from the job; docker login only writes
the registry credentials file.
Bump the CI image tag to 2.
Add ci/Dockerfile (JDK 21, Gradle 8.14.3, ffmpeg, sqlite3, node,
docker CLI and Helm) and build it as taptap/audiomanager-ci. Workflows
now start from that image instead of downloading a JDK and installing
packages on every run.
The registry namespace is the lowercased package owner `taptap`, not
`tap-tap`; update the chart, workflow and documentation accordingly.
The image build uses plain docker build/push, since the job container
starts with no buildx plugin.
- multi-stage Dockerfile with ffmpeg on Alpine JRE 21
- Helm chart for k3s: library ConfigMap, Vault users secret, data PVC,
read-only hostPath media, ingress, probes and security context
- Gitea Actions runs tests, smoke test and chart lint, then builds and
pushes the image on main and version tags