You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.
I would like to be able to configure the velero-restic-restore-helper init-container in values.yaml as part of the helm installation run.
While the image.repository setting is taken into account in assembling the velero image path, the velero-restic-restore-helper init-container image name is not affected by it. Customisation of the full qualified image name can only be done via a ConfigMap (as described here, https://velero.io/docs/master/restic/) after the fact.
This would simplify the restic based setup significantly.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.
I would like to be able to configure the velero-restic-restore-helper init-container in
values.yaml
as part of thehelm
installation run.While the
image.repository
setting is taken into account in assembling the velero image path, the velero-restic-restore-helper init-container image name is not affected by it. Customisation of the full qualified image name can only be done via a ConfigMap (as described here, https://velero.io/docs/master/restic/) after the fact.This would simplify the restic based setup significantly.
The text was updated successfully, but these errors were encountered: