Skip to content

fix(helm): switch bitnami charts from OCI to HTTPS repository#1846

Draft
jhjaggars wants to merge 1 commit into
NVIDIA:mainfrom
jhjaggars:fix/bitnami-helm-repo
Draft

fix(helm): switch bitnami charts from OCI to HTTPS repository#1846
jhjaggars wants to merge 1 commit into
NVIDIA:mainfrom
jhjaggars:fix/bitnami-helm-repo

Conversation

@jhjaggars

Copy link
Copy Markdown
Contributor

Summary

Switch Bitnami Helm chart dependencies from OCI (Docker Hub) to HTTPS repository to avoid Docker Hub rate-limiting in CI.

Related Issue

N/A — fixes recurring CI failures from unauthenticated OCI pulls.

Changes

  • Changed postgresql dependency repository from oci://registry-1.docker.io/bitnamicharts to https://charts.bitnami.com/bitnami in Chart.yaml
  • Updated Chart.lock accordingly
  • Added helm repo add bitnami to e2e scripts that install bitnami charts directly

Testing

  • mise run pre-commit passes
  • Unit tests added/updated
  • E2E tests added/updated (if applicable)

Checklist

  • Follows Conventional Commits
  • Commits are signed off (DCO)

Docker Hub OCI pulls are rate-limited and cause CI failures.
Switch postgresql dependency and e2e helm installs to use
https://charts.bitnami.com/bitnami which does not require
Docker Hub authentication.

Fixes unauthenticated OCI pull failures in CI.
@copy-pr-bot

copy-pr-bot Bot commented Jun 9, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@TaylorMutch

Copy link
Copy Markdown
Collaborator

FYI after some discussion we opted to remove the bitnami subchart. We really only added it to start testing HA setups and we aren't recommending it for production setups, instead opting for users to bring their postgres setup that fits within their operational needs. If a true need exists for bundling a postgres infrastructure into the helm chart into the future we can revisit.

@jhjaggars

Copy link
Copy Markdown
Contributor Author

Sounds good, any idea when? It'd be nice to resolve these failures in ci: #1638

@TaylorMutch

Copy link
Copy Markdown
Collaborator

I merged in the PR today on main

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