-
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
Add a parameter "uploader-type" to velero server #5062
Comments
reasonerjt
added a commit
to reasonerjt/velero
that referenced
this issue
Aug 15, 2022
This commit adds the parameter "uploader-type" to velero server, add exposes the setting via "velero install" in CLI. fixes vmware-tanzu#5062
reasonerjt
added a commit
to reasonerjt/velero
that referenced
this issue
Aug 15, 2022
This commit adds the parameter "uploader-type" to velero server, add exposes the setting via "velero install" in CLI. fixes vmware-tanzu#5062
3 tasks
reasonerjt
added a commit
to reasonerjt/velero
that referenced
this issue
Aug 16, 2022
This commit adds the parameter "uploader-type" to velero server, add exposes the setting via "velero install" in CLI. fixes vmware-tanzu#5062
reasonerjt
added a commit
to reasonerjt/velero
that referenced
this issue
Aug 16, 2022
This commit adds the parameter "uploader-type" to velero server, add exposes the setting via "velero install" in CLI. fixes vmware-tanzu#5062 Signed-off-by: Daniel Jiang <[email protected]>
ywk253100
pushed a commit
that referenced
this issue
Aug 16, 2022
This commit adds the parameter "uploader-type" to velero server, add exposes the setting via "velero install" in CLI. fixes #5062 Signed-off-by: Daniel Jiang <[email protected]> Signed-off-by: Daniel Jiang <[email protected]>
danfengliu
pushed a commit
to danfengliu/velero
that referenced
this issue
Sep 13, 2022
This commit adds the parameter "uploader-type" to velero server, add exposes the setting via "velero install" in CLI. fixes vmware-tanzu#5062 Signed-off-by: Daniel Jiang <[email protected]> Signed-off-by: Daniel Jiang <[email protected]>
We are getting an error when the pod is starting saying that the uploader-type is an unknown flag... We are running the latest version of velero (1.10) but I have tried it with v1.9 and i get the same problem.... Is there a workaround or a solution |
We are deploying via the helm chart
…On Fri, Jan 27, 2023 at 8:12 PM Raghuram Devarakonda < ***@***.***> wrote:
Can you describe how you installed Velero? You can edit the deployment and
remove the option "--uploader-type" but it is better to understand the root
cause first.
—
Reply to this email directly, view it on GitHub
<#5062 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFU7P2BSJ7GVL5DPXW3MFLTWUQT4NANCNFSM52FKPBNQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
We have it in an azure yaml pipeline which simply applies our value.yaml
file to the helm chart in your repo. We would prefer not to use a modified
helm chart though
On Sun, Jan 29, 2023 at 9:53 PM ALAN BROOKES-PLOWMAN <
***@***.***> wrote:
… We are deploying via the helm chart
On Fri, Jan 27, 2023 at 8:12 PM Raghuram Devarakonda <
***@***.***> wrote:
> Can you describe how you installed Velero? You can edit the deployment
> and remove the option "--uploader-type" but it is better to understand the
> root cause first.
>
> —
> Reply to this email directly, view it on GitHub
> <#5062 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AFU7P2BSJ7GVL5DPXW3MFLTWUQT4NANCNFSM52FKPBNQ>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add the parameter to the command line to velero server to determine the repository type during backup.
We should also make sure that the backup controller can consume this parameter to create bakcuprepsitory CR accordingly.
In this task, we'll make sure the Restic path is not broken.
The actual work to Init and connect to the Kopia repo will be covered in another issue.
The text was updated successfully, but these errors were encountered: