Open davidfrickert opened 2 months ago
I faced the same problem and managed to work around it by creating a secret where the key referenced is empty.
# Not sure if it's necessary, so watch out for empty space at the end
kubectl -n vaultwarden create secret generic vaultwarden-disable-admin --from-literal=token=
adminToken:
existingSecret: "vaultwarden-disable-admin"
existingSecretKey: "token"
Trying to use this chart to replace another old one that i was using but running into issues...
The docs recommend setting
adminToken=null
to disable admin token but this does not work because because thesecrets.yaml
template tries to read.Values.adminToken.existingSecret
which doesn't work becauseadminToken
is null.Setting
adminToken.value
to null also does not work as the chart tries to use the existing secret which i also do not want to use in the_podSec.tpl
.