forked from vikunja/helm-chart
Update README: add instructions for the use of secrets
Signed-off-by: CAMPION Hugo <h.campion@geco-it.fr>
This commit is contained in:
parent
9bb51e1666
commit
1583ce39c8
25
README.md
25
README.md
|
@ -85,6 +85,31 @@ If you need to create another user, you could opt to execute the following comma
|
|||
./vikunja user create --email <user@email.com> --user <user1> --password <password123>
|
||||
```
|
||||
|
||||
### Utilizing secrets for `env` and `config.yml`
|
||||
|
||||
Each env in the stack can be sourced from a secret in your `values.yaml`:
|
||||
|
||||
```yaml
|
||||
api:
|
||||
env:
|
||||
VIKUNJA_DATABASE_PASSWORD:
|
||||
valueFrom:
|
||||
secretKeyRef:
|
||||
name: vikunja-env
|
||||
key: VIKUNJA_DATABASE_PASSWORD
|
||||
```
|
||||
If your vikunja config needs to contain sensible data, like oauth config, you can source it from a secret in your `values.yaml`:
|
||||
|
||||
```yaml
|
||||
api:
|
||||
persistence:
|
||||
config:
|
||||
enabled: true
|
||||
type: secret
|
||||
mountPath: /etc/vikunja/config.yml
|
||||
# Warning, you can not choose the secret name here, it will search for {{ Release.Name }}-api-config ! So please create your secret accordingly !
|
||||
```
|
||||
|
||||
## Publishing
|
||||
|
||||
The following steps are automatically performed when a git tag for a new version is pushed to the repository.
|
||||
|
|
Loading…
Reference in New Issue