vaultwarden helm template
This commit is contained in:
@@ -8,3 +8,4 @@ helmCharts:
|
||||
version: 0.31.8
|
||||
releaseName: vaultwarden
|
||||
namespace: vaultwarden
|
||||
valuesFile: values.yaml
|
||||
@@ -294,13 +294,12 @@ storage:
|
||||
## @param storage.data Data directory configuration, refer to values.yaml for parameters.
|
||||
##
|
||||
data:
|
||||
{}
|
||||
# name: "vaultwarden-data"
|
||||
# size: "15Gi"
|
||||
# class: ""
|
||||
# path: "/data"
|
||||
# keepPvc: false
|
||||
# accessMode: "ReadWriteOnce"
|
||||
name: vaultwarden-data
|
||||
size: 1Gi
|
||||
class: openebs-3-replicas
|
||||
path: /data
|
||||
keepPvc: false
|
||||
accessMode: ReadWriteOnce
|
||||
|
||||
## @param storage.attachments Attachments directory configuration, refer to values.yaml for parameters.
|
||||
## By default, attachments/ is located inside the data directory.
|
||||
@@ -373,7 +372,7 @@ pushNotifications:
|
||||
enabled: false
|
||||
## @param pushNotifications.existingSecret Name of an existing secret containing the Bitwarden installation id and key
|
||||
##
|
||||
existingSecret: ""
|
||||
existingSecret: vaultwarden
|
||||
installationId:
|
||||
## @param pushNotifications.installationId.value Bitwarden installation id string
|
||||
## Example: installationIdGoesHere
|
||||
@@ -382,7 +381,7 @@ pushNotifications:
|
||||
## @param pushNotifications.installationId.existingSecretKey When using an existing secret, specify the key which contains the installation id.
|
||||
## Example: INSTALLATION_ID
|
||||
##
|
||||
existingSecretKey: ""
|
||||
existingSecretKey: PUSH_INSTALLATION_ID
|
||||
installationKey:
|
||||
## @param pushNotifications.installationKey.value Bitwarden installation key string
|
||||
## Example: superSecretInstallationKey
|
||||
@@ -391,7 +390,7 @@ pushNotifications:
|
||||
## @param pushNotifications.installationKey.existingSecretKey When using an existing secret, specify the key which contains the installation key.
|
||||
## Example: INSTALLATION_KEY
|
||||
##
|
||||
existingSecretKey: ""
|
||||
existingSecretKey: PUSH_INSTALLATION_KEY
|
||||
## @param pushNotifications.relayUri Change Bitwarden relay uri.
|
||||
## Refer to https://github.com/dani-garcia/vaultwarden/wiki/Enabling-Mobile-Client-push-notification for details
|
||||
##
|
||||
@@ -430,7 +429,7 @@ eventsDayRetain: ""
|
||||
## @param domain Domain name where the application is accessed
|
||||
## Example: https://warden.contoso.com:8443
|
||||
##
|
||||
domain: ""
|
||||
domain: "https://vault.borninpain.de"
|
||||
|
||||
## @param sendsAllowed Controls whether users are allowed to create Bitwarden Sends.
|
||||
##
|
||||
@@ -548,7 +547,7 @@ iconBlacklistNonGlobalIps: "true"
|
||||
## - "browser-fileless-import": Directly import credentials from other providers without a file.
|
||||
## - "fido2-vault-credentials": Enable the use of FIDO2 security keys as second factor.
|
||||
##
|
||||
experimentalClientFeatureFlags: null
|
||||
experimentalClientFeatureFlags: ssh-key-vault-item,ssh-agent
|
||||
|
||||
## @param requireDeviceEmail Require new device emails. When a user logs in an email is required to be sent.
|
||||
##
|
||||
@@ -575,11 +574,11 @@ adminToken:
|
||||
## @param adminToken.existingSecret Specify an existing Kubernetes secret containing the admin token. Also set adminToken.existingSecretKey.
|
||||
## Example: admincreds_secret
|
||||
##
|
||||
existingSecret: ""
|
||||
existingSecret: vaultwarden
|
||||
## @param adminToken.existingSecretKey When using adminToken.existingSecret, specify the key containing the token.
|
||||
## Example: ADMIN_TOKEN
|
||||
##
|
||||
existingSecretKey: ""
|
||||
existingSecretKey: ADMIN_TOKEN
|
||||
## @param adminToken.value Plain or argon2 string containing the admin token.
|
||||
## This example is the argon2 has of "R@ndomTokenString" (no quotes).
|
||||
##
|
||||
@@ -596,7 +595,7 @@ adminRateLimitMaxBurst: "3"
|
||||
## @param timeZone Specify timezone different from the default (UTC).
|
||||
## For example: "Europe/Berlin"
|
||||
##
|
||||
timeZone: ""
|
||||
timeZone: Europe/Berlin
|
||||
|
||||
## @section BETA Features
|
||||
##
|
||||
@@ -616,7 +615,7 @@ yubico:
|
||||
clientId: ""
|
||||
## @param yubico.existingSecret Name of an existing secret containing the Yubico secret key. Also set yubico.secretKey.existingSecretKey.
|
||||
##
|
||||
existingSecret: ""
|
||||
existingSecret: vaultwarden
|
||||
## Yubico secret key
|
||||
##
|
||||
secretKey:
|
||||
@@ -627,7 +626,7 @@ yubico:
|
||||
## @param yubico.secretKey.existingSecretKey When using an existing secret, specify the key which contains the secretKey.
|
||||
## Example: YUBICO_SECRET_KEY
|
||||
##
|
||||
existingSecretKey: ""
|
||||
existingSecretKey: YUBICO_SECRET_KEY
|
||||
## @param yubico.server Specify a Yubico server, otherwise the default servers will be used
|
||||
##
|
||||
server: ""
|
||||
@@ -641,7 +640,7 @@ duo:
|
||||
iKey: ""
|
||||
## @param duo.existingSecret Name of an existing secret containing the Duo skey. Also set duo.sKey.existingSecretKey.
|
||||
##
|
||||
existingSecret: ""
|
||||
existingSecret: vaultwarden
|
||||
## Duo secret key
|
||||
##
|
||||
sKey:
|
||||
@@ -652,7 +651,7 @@ duo:
|
||||
## @param duo.sKey.existingSecretKey When using an existing secret, specify the key which contains the sKey.
|
||||
## Example: DUO_SKEY
|
||||
##
|
||||
existingSecretKey: ""
|
||||
existingSecretKey: DUO_SKEY
|
||||
## @param duo.hostname Duo API hostname
|
||||
##
|
||||
hostname: ""
|
||||
@@ -662,10 +661,10 @@ duo:
|
||||
smtp:
|
||||
## @param smtp.existingSecret Name of an existing secret containing the SMTP username and password. Also set smtp.username.existingSecretKey and smtp.password.existingSecretKey.
|
||||
##
|
||||
existingSecret: ""
|
||||
existingSecret: vaultwarden
|
||||
## @param smtp.host SMTP host
|
||||
##
|
||||
host: ""
|
||||
host: "mxe965.netcup.net"
|
||||
## @param smtp.security SMTP Encryption method
|
||||
## Possible values:
|
||||
## - starttls: explicit TLS using ports 587 or 25
|
||||
@@ -675,14 +674,14 @@ smtp:
|
||||
security: "starttls"
|
||||
## @param smtp.port SMTP port
|
||||
##
|
||||
port: 25
|
||||
port: 587
|
||||
## @param smtp.from SMTP sender email address
|
||||
## Example: juan.delacruz@gmail.com
|
||||
##
|
||||
from: ""
|
||||
from: noreply@borninpain.de
|
||||
## @param smtp.fromName SMTP sender FROM
|
||||
##
|
||||
fromName: ""
|
||||
fromName: Vaultwarden
|
||||
## Username for SMTP authentication.
|
||||
##
|
||||
username:
|
||||
@@ -693,7 +692,7 @@ smtp:
|
||||
## @param smtp.username.existingSecretKey When using an existing secret, specify the key which contains the username.
|
||||
## Example: SMTP_USERNAME
|
||||
##
|
||||
existingSecretKey: ""
|
||||
existingSecretKey: SMTP_USERNAME
|
||||
## Password for SMTP authentication.
|
||||
##
|
||||
password:
|
||||
@@ -704,7 +703,7 @@ smtp:
|
||||
## @param smtp.password.existingSecretKey When using an existing secret, specify the key which contains the password.
|
||||
## Example: SMTP_PASSWORD
|
||||
##
|
||||
existingSecretKey: ""
|
||||
existingSecretKey: SMTP_PASSWORD
|
||||
## @param smtp.authMechanism SMTP authentication mechanism
|
||||
## Possible values: "Plain", "Login", "Xoauth2"
|
||||
## Multiple options need to be separated by a comma. (not tested)
|
||||
|
||||
Reference in New Issue
Block a user