Update Ironbank

This MR contains the following updates:

Package	Update	Change
bb-common	patch	0.14.0 -> 0.14.1
gluon	patch	0.9.7 -> 0.9.8
harbor (source)	patch	1.18.2 -> 1.18.3
postgresql (source)	minor	18.2.3 -> 18.5.14
redis (source)	major	24.1.0-bb.0 -> 25.3.2-bb.0
registry1.dso.mil/ironbank/opensource/goharbor/harbor-core (source)	minor	v2.14.2 -> v2.15.0
registry1.dso.mil/ironbank/opensource/goharbor/harbor-core (source)	minor	2.14.2 -> 2.15.0
registry1.dso.mil/ironbank/opensource/goharbor/harbor-exporter (source)	minor	v2.14.2 -> v2.15.0
registry1.dso.mil/ironbank/opensource/goharbor/harbor-jobservice (source)	minor	v2.14.2 -> v2.15.0
registry1.dso.mil/ironbank/opensource/goharbor/harbor-portal (source)	minor	v2.14.2 -> v2.15.0
registry1.dso.mil/ironbank/opensource/goharbor/harbor-registryctl (source)	minor	v2.14.2 -> v2.15.0
registry1.dso.mil/ironbank/opensource/goharbor/registry (source)	minor	v2.14.2 -> v2.15.0
registry1.dso.mil/ironbank/opensource/goharbor/trivy-adapter (source)	minor	v2.14.2 -> v2.15.0
registry1.dso.mil/ironbank/opensource/nginx/nginx (source)	patch	1.29.4 -> 1.29.6
registry1.dso.mil/ironbank/opensource/postgres/postgresql (source)	minor	18.1 -> 18.3
registry1.dso.mil/ironbank/opensource/redis/redis8-slim (source)	minor	8.4.0 -> 8.6.1

Complete MR checklist

Assignee

• Followed upgrade instructions outlined in docs/DEVELOPMENT_MAINTENANCE.md
• Update Docs with new/updated steps as needed
• Tested and Validated Changes made with supporting info like logs or screenshots from test pipelines

Add supporting info below

k3d-dev upgrade test successful (1.18.2-bb.0 -> 1.18.3-bb.0):

HelmReleases (18/18 True, harbor upgraded):

Docker login/push/pull to Harbor registry:

Harbor UI - Dashboard (admin login, library project with pushed image):

Prometheus targets (harbor 5/5 UP confirmed via API):

Reviewer only

• Tested and Validated changes

---

Release Notes

goharbor/harbor-helm (harbor)

v1.18.3

Compare Source

Harbor OSS version: v2.14.3

What's Changed

Other Changes

• Bump version to 1.18.3, appVersion to 2.14.3 by @alanrichman in https://github.com/goharbor/harbor-helm/pull/2327

New Contributors

• @alanrichman made their first contribution in https://github.com/goharbor/harbor-helm/pull/2327

Full Changelog: https://github.com/goharbor/harbor-helm/compare/v1.18.2...v1.18.3

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This MR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this MR, check this box

---

This MR was automatically generated by Renovate Bot.

Upgrade Notices

Known upstream bug (goharbor/harbor#22996): The IronBank v2.15.0 image was built before upstream fix PR #22998 was cherry-picked to the release branch. The ca_certificate column addition was incorrectly placed in migration 0171 (a v2.14.1 file) instead of a new 0180 file. When upgrading from v2.14.x, golang-migrate skips the modified 0171 since the schema is already at version 171, causing the Registries page to return "internal server error" (column t0.ca_certificate does not exist).

Workaround: After upgrade, run against the Harbor database:

ALTER TABLE registry ADD COLUMN IF NOT EXISTS ca_certificate TEXT;

Then restart harbor-core pods. This will self-resolve when IB rebuilds from the final v2.15.0 tag which includes migration 0180_2.15.0_schema.up.sql.

Linked issues

Closes #170 (closed)