ANNOUNCEMENT: Repository moving to bitnami/sealed-secrets – Action Required for Helm Users

[agarcia-oss]

Context

To consolidate our projects and streamline maintenance, we will be migrating the sealed-secrets repository from the bitnami-labs organization to the main bitnami organization.

• Current Location: github.com/bitnami-labs/sealed-secrets
• Target Location: github.com/bitnami/sealed-secrets

Timeline

The migration is scheduled to take place on Monday June 15th.

---

What Breaks & Action Required

While GitHub will automatically redirect standard Git commands (git clone, git fetch) and browser links to the new organization, GitHub Pages URLs will not redirect. This directly impacts Helm chart installations.

1. If you use Helm (or GitOps tools like Flux / Argo CD)

The current Helm repository URL (https://bitnami-labs.github.io/sealed-secrets) will return a 404 error immediately after the migration.

Action Required: You must update your Helm repository URLs to point to the new bitnami organization namespace.

• Standard Helm CLI:

# Remove the old repo
helm repo remove sealed-secrets

# Add the new repo URL
helm repo add sealed-secrets [https://bitnami.github.io/sealed-secrets](https://bitnami.github.io/sealed-secrets)
helm repo update

• Flux CD (HelmRepository CRD):
  Update your manifest's spec URL:

apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: HelmRepository
metadata:
  name: sealed-secrets
spec:
  interval: 1h
  url: [https://bitnami.github.io/sealed-secrets](https://bitnami.github.io/sealed-secrets) # <-- Update here

• Argo CD (Application source):
  Update the repoURL in your Application definitions to point to https://bitnami.github.io/sealed-secrets.

2. If you download kubeseal via scripts or CI pipelines

GitHub will natively handle redirects for Release asset downloads (e.g., github.com/bitnami-labs/.../releases/download/...). However, some strict network clients or downloading tools that do not follow HTTP redirects (-L in curl) may fail.

Action Required: We highly recommend updating your installation scripts and CI pipelines to target the new URL directly:
https://github.com/bitnami/sealed-secrets/...

3. If you develop/contribute to Sealed Secrets locally

Your existing local git remotes will continue to work via GitHub's backend redirects.

Action Required (Optional but recommended): Update your local remote URL to prevent any future naming collision issues:

git remote set-url origin [https://github.com/bitnami/sealed-secrets.git](https://github.com/bitnami/sealed-secrets.git)

Questions or Concerns?

Please leave a comment below if you have any questions or if this migration presents a blocking issue for your current deployment pipelines so we can help accommodate. Thank you for your continued support!

[agarcia-oss]

#1983 to address all the organization migration changes

[rouke-broersma]

Just to confirm, does this have any relation to bitnami secure images or are sealed-secrets images still exempt from that?

[agarcia-oss]

Hi @rouke-broersma these changes only affect the GitHub repository and it should be transparent to most users.

The Sealed Secrets Dockerhub images remain unaffected.