bitwarden/helm-charts

---

Bitwarden Client Applications

This repository houses all Bitwarden client applications except the Mobile application.

Please refer to the Clients section of the Contributing Documentation for build instructions, recommended tooling, code style tips, and lots of other great information to get you started.

Related projects:

• bitwarden/server: The core infrastructure backend (API, database, Docker, etc).
• bitwarden/mobile: The mobile app vault (iOS and Android).
• bitwarden/directory-connector: A tool for syncing a directory (AD, LDAP, Azure, G Suite, Okta) to an organization.

We're Hiring!

Interested in contributing in a big way? Consider joining our team! We're hiring for many positions. Please take a look at our Careers page to see what opportunities are currently open as well as what it's like to work at Bitwarden.

Contribute

Code contributions are welcome! Please commit any pull requests against the main branch. Learn more about how to contribute by reading the Contributing Guidelines. Check out the Contributing Documentation for how to get started with your first contribution.

Security audits and feedback are welcome. Please open an issue or email us privately if the report is sensitive in nature. You can read our security policy in the SECURITY.md file.

helm-charts's Issues

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update actions/upload-artifact action to v4

Detected dependencies

github-actions

.github/workflows/build.yml

• actions/checkout v4.1.1@b4ffde65f46336ab88eb53be808477a3936bae11
• Azure/setup-helm v3.5@5119fcb9089d432beecbf79bb2c7915207344b78
• Azure/login v1.6.0@e15b166166a8746d1a47596803bd8c1b595455cf
• actions/upload-artifact v3.1.3@a8a3f3ad30e3422c9c7b888a15615d19a852ae32
• ubuntu 22.04

.github/workflows/linter.yml

• actions/checkout v4.1.1@b4ffde65f46336ab88eb53be808477a3936bae11
• Azure/setup-helm v3.5@5119fcb9089d432beecbf79bb2c7915207344b78
• actions/setup-python v5.0.0@0a5c61591373683505ea898e09a3ea4f39ef2b9c
• helm/chart-testing-action v2.6.1@e6669bcd63d7cb57cb4380c33043eebe5d111992
• ubuntu 22.04

.github/workflows/release.yml

• actions/checkout v4.1.1@b4ffde65f46336ab88eb53be808477a3936bae11
• Azure/login v1.6.0@e15b166166a8746d1a47596803bd8c1b595455cf
• crazy-max/ghaction-import-gpg v6.1.0@01dd5d3ca463c7f10f7f4f7b4f177225ac661ee4
• Azure/setup-helm v3.5@5119fcb9089d432beecbf79bb2c7915207344b78
• helm/chart-releaser-action v1.5.0@be16258da8010256c6e82849661221415f031968
• ubuntu 22.04

.github/workflows/tests.yml

• actions/checkout v4.1.1@b4ffde65f46336ab88eb53be808477a3936bae11
• Azure/setup-helm v3.5@5119fcb9089d432beecbf79bb2c7915207344b78
• actions/setup-python v5.0.0@0a5c61591373683505ea898e09a3ea4f39ef2b9c
• helm/chart-testing-action v2.6.1@e6669bcd63d7cb57cb4380c33043eebe5d111992
• helm/kind-action v1.8.0@dda0770415bac9fc20092cacbc54aa298604d140
• ubuntu 22.04

.github/workflows/update-versions.yml

• actions/checkout v4.1.1@b4ffde65f46336ab88eb53be808477a3936bae11
• actions/checkout v4.1.1@b4ffde65f46336ab88eb53be808477a3936bae11
• actions/checkout v4.1.1@b4ffde65f46336ab88eb53be808477a3936bae11
• ubuntu 22.04
• ubuntu 22.04

.github/workflows/version-bump.yml

• actions/checkout v4.1.1@b4ffde65f46336ab88eb53be808477a3936bae11
• Azure/login v1.6.0@e15b166166a8746d1a47596803bd8c1b595455cf
• crazy-max/ghaction-import-gpg v6.1.0@01dd5d3ca463c7f10f7f4f7b4f177225ac661ee4
• ubuntu 22.04

---

• Check this box to trigger a request for Renovate to run again on this repository

Helm install fail du to resources field duplciated on scim deployment

Steps To Reproduce

use flux to deploy the helm release;

Expected Result

Helm release is well deployed

Actual Result

✗ Helm install failed: error while running post render on files: map[string]interface {}(nil): yaml: unmarshal errors:
  line 54: mapping key "resources" already defined at line 53

Screenshots or Videos

No response

Additional Context

No response

Chart Version

self-host-0.1.7-Beta

Environment Details

No response

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

MSSQL pod fail on crashloopBackOff

Steps To Reproduce

deploy minimal helm values:

database:
  enabled: true
  volume:
    backups:
      size: 20Gi
    data:
      size: 20Gi
    log:
      size: 10Gi
general:
  admins: xxxx
  domain: bitwarden.env.fr
  email:
    replyToEmail: [email protected]
    smtpHost: toto.env.fr
    smtpPort: "587"
  volumeAccessMode: ReadWriteOnce
secrets:
  secretName: custom

Expected Result

mssql pod is up and running

Actual Result

mssql log:

SQL Server 2019 will run as non-root by default.
This container is running as user mssql.
To learn more visit https://go.microsoft.com/fwlink/?linkid=2099216.
2023-12-04 16:54:47.94 Server      The licensing PID was successfully processed. The new edition is [Express Edition].
2023-12-04 16:54:48.81 Server      Setup step is copying system data file 'C:\templatedata\master.mdf' to '/var/opt/mssql/data/master.mdf'.
2023-12-04 16:54:48.82 Server      ERROR: Setup FAILED copying system data file 'C:\templatedata\master.mdf' to '/var/opt/mssql/data/master.mdf':  5(Access is denied.)
ERROR: BootstrapSystemDataDirectories() failure (HRESULT 0x80070005)
Stream closed EOF for bitwarden/bitwarden-self-host-mssql-0 (bitwarden-self-host-mssql)

kube event:

    state:
      waiting:
        message: back-off 5m0s restarting failed container=bitwarden-self-host-mssql
          pod=bitwarden-self-host-mssql-0_bitwarden(61aea36e-717f-4732-81ff-ab64ca6bbc90)
        reason: CrashLoopBackOff

Screenshots or Videos

No response

Additional Context

No response

Chart Version

self-host-0.1.7-Beta

Environment Details

kubernetes self-hosted: 1.22.2

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Cannot find preset's package (github>bitwarden/renovate-config:pin-actions)

SSO - 404

Steps To Reproduce

Steps To Reproduce

1. Go to 'https://bitwarden/#/sso
2. Click on 'Login.'
3. Login with SSO (SAML 2)

Log:
self-host-web pod

info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 GET http://bitwarden.xxxx.xx/Account/Login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3Fclient_id%3Dweb%26redirect_uri%3Dhttps%253A%252F%252Fbitwarden.xxxx.xx%252Fsso-connector.html%26response_type%3Dcode%26scope%3Dapi%2520offline_access%26state%3DzPXULyXRcXD5hdeh4kEZtjDgF9fH5ULPL3giu4GDNR7JSgwh896a4a2BhfTXvFF9_identifier%253DKIF%25C3%259C%26code_challenge%3D4YNnYCgAKaCVZYu_mljIsSgWcPdQC1kP38mMRbeZA8o%26code_challenge_method%3DS256%26response_mode%3Dquery%26domain_hint%3DKIF%25C3%259C%26ssoToken%3DBWUserPrefix_CfDJ8MIpcSLm3NdOhzBWDFQa2p_ExYcHORWE1RjVO6sVwIVN6jkWIgxXZX-oknRiJCszX0oZLqbMEtAc1Cqek8AbKNi61MnqGGjkDtrigfSgjwnDqJIQMsW5vuuQjXwwP2D9sEF0qe9wBGWsfa8qHqFD9Qb24nhQk1wv8Wz65s3w_K1o7knB-2VBHLiDM7X2Vw6jBI0e206BOMh9F3kZLiHUysG6kxEpHWDipZtV_c_czVv6a1EmGqlw-2mZAfqjbl6l5-vl58IoNjfEZW9G-Id1BWk4lrpf11a9zjfkGsRdg1jYZR0c_QKNPwr4z6jZ7NUIhA - - - 404 0 - 0.2309ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]

Expected Result

Successful Login

Actual Result

Login not successful - 404 error

Screenshots or Videos

No response

Additional Context

No response

Chart Version

0.1.2-Beta

Environment Details

No response

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

Helm install fail with database statefulset

Steps To Reproduce

run this cmd:

helm install bitwarden bitwarden/self-host --version=0.1.7-Beta  --namespace bitwarden --values values.yaml

with this minimal values:

database:
  enabled: true
  volume:
    backups:
      size: 20Gi
    data:
      size: 20Gi
    log:
      size: 10Gi
general:
  admins: false
  domain: test.env.fr
  email:
    replyToEmail: [email protected]
    smtpHost: xxxxx
    smtpPort: "587"
  ingress:
    annotations:
    enabled: true
secrets:
  secretName: custom

Expected Result

Helm release is deployed

Actual Result

Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(StatefulSet.spec): missing required field "serviceName" in io.k8s.api.apps.v1.StatefulSetSpec

Screenshots or Videos

No response

Additional Context

No response

Chart Version

0.1.7-Beta

Environment Details

No response

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

Service Temporarily unavailable 503 on clicking send verify email

Steps To Reproduce

1. Configure the bitwarden in the cluster
2. Create an admin account
3. Login
4. CLick on "Send email" to verify the email
5. Got an error "Service Temporarily unavailable 503"

Expected Result

I received the first email after I create the account, so my SMPT is working, I expect to receive the verification email

Actual Result

Error received instead

Screenshots or Videos

Additional Context

No response

Chart Version

0.1.14-Beta

Environment Details

Using EKS as kubernetes environment and Amazon SES to send emails

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.