A Helm chart for deploying a Bitwarden instance on Kubernetes
⚠️ Self-host Helm chart v2.3.3 removes the legacy ghcr.io/bitwarden/helm-charts/kubectl image ⚠️
This release removes the legacy ghcr.io/bitwarden/helm-charts/kubectl image from GHCR. The image has known security vulnerabilities and stopped receiving patches once it was replaced as the chart's default in v1.1.10. If your values.yaml still references it, review the action below before running helm upgrade.
🚨 ghcr.io/bitwarden/helm-charts/kubectl image removed from GHCR
The supportComponents.kubectl component moved to alpine/kubectl as its default image in v1.1.10. The old ghcr.io/bitwarden/helm-charts/kubectl image was left in place for backward compatibility. As of this release, it has been deleted from GHCR.
You are affected if either applies:
- Your
values.yamlexplicitly setssupportComponents.kubectl.image.repositorytoghcr.io/bitwarden/helm-charts/kubectl. - You installed the chart before v1.1.10 and never overrode
supportComponents.kubectl, so your release is still pinned to the old image tag from that install.
Action Required
Check your values.yaml for a supportComponents.kubectl override pointing at the ghcr image:
# Remove this override
supportComponents:
kubectl:
image:
repository: ghcr.io/bitwarden/helm-charts/kubectl
tag: <any tag>Remove the override, or point it at the chart's current default, so the chart uses the maintained image:
supportComponents:
kubectl:
image:
repository: alpine/kubectl
tag: 1.36.3If you have no override and are running a chart version ≥ 1.1.10, no action is needed: you're already on alpine/kubectl.
What's Changed
- Update self-host versions: core 2026.8.0, web 2026.8.0 by @app/bre-deploy in #592
Full Changelog: self-host-2.3.2...self-host-2.3.3