-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Activate --default-volumes-to-restic without reinstalling #2781
Comments
@Panplumousse Thanks for asking for this feature. |
Hello yes i have check that but i use schedule for backup and i dont know where put this flag option in schedule yaml |
Wrt schedules, the |
To answer the question about modifying the velero deployment, you can use
|
@ashish-amarnath @nrb thx a lot |
@Panplumousse the $ kubectl -n velero get deploy velero -ojson | jq .spec.template.spec.containers[0].args
[
"server",
"--features=",
"--default-volumes-to-restic=true"
]
$ kubectl -n velero get deploy velero -ojson | jq .spec.template.spec.containers[0].args[2]
"--default-volumes-to-restic=true" |
@ashish-amarnath thx for your feed back from which version of velero this functionality is present I am currently in 1.3.2 Error: unknown flag: --default-volumes-to-restic thx a lot |
@ashish-amarnath ok thx a lot |
@Panplumousse I don't think there is any further action item on this PR. I'll close this out. Feel free to reach out if you have more questions. |
Describe the problem/challenge you have
Is not really a problem is a question about velero installation
Describe the solution you'd like
I am using velero / restic in production and would like to change the way volumes are backed up.
I would like to activate the option: --default-volumes-to-restic
without reinstalling velero, maybe by modifying the velero "deploy".
Could you tell me how can imake this modification
thank you in advance
The text was updated successfully, but these errors were encountered: