Add support for secret env vars

[dunglas]

This PR adds a new value credentials.extraEnvVars allowing to store data in a secret and expose it to the container through an environment variable.
This is necessary for the Digital Ocean plugin and maybe other.

I tested it (and it works). This PR also includes #94 (because without this PR, the chart is broken). I'll rebase when #94 will be merged.

Thanks for this great tool by the way!

[carlisia]

This lgtm!

@skriss should this also go on therestic-daemonset template?

[skriss]

@carlisia yeah, I think it probably should, since the secret is mounted in there too so presumably any extra env vars apply there as well.

[carlisia]

Ok @dunglas, please also add it to the restic-daemonset template when you have a chance.

[dunglas]

@carlisia done! Thanks for the review.

[carlisia]

Awesome, and thanks for adding .Values.configuration.extraEnvVars to the restic template too!

👍

[skriss]

LGTM, thanks for the PR @dunglas!

[qRoC]

Hello.

variables such as "DIGITALOCEAN_TOKEN: <your-key>".

What is <your-key>?

For configuration:

credentials:
  existingSecret: velero-secrets
  extraEnvVars:
    DIGITALOCEAN_TOKEN: 'hello'

Need generate 2 secrets: velero-secrets and velero?

Because is generate:

- name: DIGITALOCEAN_TOKEN
  valueFrom:
    secretKeyRef:
       name: velero
       key: DIGITALOCEAN_TOKEN

[mshivanna]

In deployment.yaml file on line 129 under secretKeyRef

name: {{ include "velero.fullname" $ }}

should have been

name: {{ include "velero.secretName" $ }}