Skip to content

Chore/fix ci pipeline - #121

Merged
pancysingla-creator merged 4 commits into
mainfrom
chore/fix-ci-pipeline
Nov 18, 2026
Merged

pancysingla-creator merged 4 commits into
mainfrom
chore/fix-ci-pipeline

Conversation

@pancysingla-creator

Copy link
Copy Markdown
Contributor

What

Fixes the CI pipeline, which is currently failing on main.

  • it-test-api / docker compose: use bitnamilegacy/postgresql:14.5.0. Bitnami removed versioned images from bitnami/ on Docker Hub.
  • e2e: k3d install: pin k3d-version: v5.6.0. k3d's install script now downloads checksums.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.
  • e2e: image push: push to the local registry via 127.0.0.1:5000. The runner's Docker only allows plain HTTP to loopback IPs, not to the registry.localhost hostname. The cluster still pulls from LOCAL_REGISTRY (registry.localhost:5000), which k3d configures for HTTP inside the nodes.
  • e2e: helm postgres: override the chart's default bitnami/postgresql:11.5.0-debian-9-r84, which is no longer on Docker Hub, with bitnamilegacy/postgresql:11.22.0.

pancysingla-creator and others added 4 commits November 17, 2026 12:48
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 anantadwi13 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm. thanks

@pancysingla-creator
pancysingla-creator merged commit 52bf4ac into main Nov 18, 2026
8 checks passed
@pancysingla-creator
pancysingla-creator deleted the chore/fix-ci-pipeline branch November 18, 2026 07:29

This branch was successfully deployed

1 active deployment
manual — d9e7db20 Deployed Nov 18, 2026 by pancysingla-creator via publish-docker #449
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants