Repository navigation
Chore/fix ci pipeline - #121
Merged
Merged
Conversation
Bitnami removed its versioned images from Docker Hub, so bitnami/postgresql:14.5.0 no longer resolves and `make it-test-api` fails at `docker compose up -d postgres`. The same image is still published under bitnamilegacy/. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
k3d-action installs k3d through k3d's latest install.sh, which now also downloads checksums.txt from the release. k3d v5.2.2 (the action's default) never published that file, so the install failed with a 404. v5.6.0 publishes it. k3d v5.6.0 starts a newer k3s that no longer accepts --no-deploy, so metrics-server is disabled with the equivalent --disable flag. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The k3d registry at registry.localhost:5000 only serves plain HTTP. Docker on the runner now tries HTTPS for that hostname and fails with "server gave HTTP response to HTTPS client". Docker always allows plain HTTP for loopback IPs, so push through 127.0.0.1:5000 instead. It is the same registry, so the cluster still pulls from registry.localhost:5000. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The MLP chart depends on stable/postgresql 7.0.2, whose default image bitnami/postgresql:11.5.0-debian-9-r84 is no longer on Docker Hub (and was not copied to bitnamilegacy). The postgres pod cannot start, so `helm install --wait` times out. Use bitnamilegacy/postgresql:11.22.0, the latest Postgres 11 image that is still published. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
anantadwi13
self-requested a review
November 18, 2026 07:20
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Fixes the CI pipeline, which is currently failing on
main.bitnamilegacy/postgresql:14.5.0. Bitnami removed versioned images frombitnami/on Docker Hub.k3d-version: v5.6.0. k3d's install script now downloadschecksums.txt, which the action's default v5.2.2 release doesn't have. The newer k3s drops--no-deploy, so metrics-server is disabled with--disable.127.0.0.1:5000. The runner's Docker only allows plain HTTP to loopback IPs, not to theregistry.localhosthostname. The cluster still pulls fromLOCAL_REGISTRY(registry.localhost:5000), which k3d configures for HTTP inside the nodes.bitnami/postgresql:11.5.0-debian-9-r84, which is no longer on Docker Hub, withbitnamilegacy/postgresql:11.22.0.