Add kustomize to the base image #32

Merged

GuillaumeHemmen merged 1 commit from add-kustomize-to-base into master

2026-10-16 18:29:31 +00:00

claude-bot commented

2026-10-16 18:18:11 +00:00

Member

forgejo#14 renders its manifests with Kustomize before running kubeconform and kube-linter. sindri:ci-26.30.0 (and ci-26.42.0) has neither kustomize nor kubectl, so the render step exits 127 and both lint jobs fail in a few seconds.

This adds kustomize v5.8.2 to the pinned QA block in the base stage, next to kubeconform and kube-linter, and checks it runs at build time.

Tested: the same install command inside sindri:ci-26.42.0 prints v5.8.2. I did not run a full image build.

After merge: tag a release so docker-tag publishes a new ci- image, then forgejo#14 moves to that tag.

🤖 Generated with Claude Code

forgejo#14 renders its manifests with Kustomize before running kubeconform and kube-linter. `sindri:ci-26.30.0` (and `ci-26.42.0`) has neither `kustomize` nor `kubectl`, so the render step exits 127 and both lint jobs fail in a few seconds. This adds kustomize v5.8.2 to the pinned QA block in the base stage, next to kubeconform and kube-linter, and checks it runs at build time. Tested: the same install command inside `sindri:ci-26.42.0` prints `v5.8.2`. I did not run a full image build. After merge: tag a release so `docker-tag` publishes a new `ci-` image, then forgejo#14 moves to that tag. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

claude-bot added 1 commit

2026-10-16 18:18:11 +00:00

Add kustomize to the base image

/ docker-dev-ci (push) Successful in 3m25s

Details

/ docker-dev-coder (push) Successful in 4m2s

Details

/ docker-dev-coder-xfce-vnc (push) Successful in 11m22s

Details

8c60181aa6

forgejo#14 renders its manifests with Kustomize before linting them, so
kubeconform and kube-linter check what Argo CD applies. The ci image ships
neither kustomize nor kubectl, so the render step exits 127 and both lint jobs
fail before linting anything.

kustomize is a static binary with no cluster-version coupling, so it goes in
the same pinned block as kubeconform and kube-linter.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>