Installing v1.0.0 failing with error NoCredentialProviders #2279
Comments
|
|
|
@stalinbritto could you provide the following outputs:
|
|
@stalinbritto just checking in to see if you were able to resolve this or could provide more info. |
|
same here: Error installing Velero. Use |
|
Issue has been resolved, after delete namespace and reinstall velero.
…On Fri, 21 Feb 2020, 8:59 pm Steve Kriss, ***@***.***> wrote:
@stalinbritto <https://github.com/stalinbritto> just checking in to see
if you were able to resolve this or could provide more info.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2279?email_source=notifications&email_token=ALNFFOVW7XIT2LGBKMPILPTRD7XMLA5CNFSM4KWNBHCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMTCI7A#issuecomment-589702268>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALNFFOXMUXGTGNPM6J4YYWTRD7XMLANCNFSM4KWNBHCA>
.
|
|
Hi,
Velero 1.0.0 is not working in after k8s 1.14 v
Velero 1.2.0 working latest k8s version
…On Sat, 22 Feb 2020, 3:05 pm billhoph, ***@***.***> wrote:
same here:
Waiting for resources to be ready in cluster...
Namespace/velero: attempting to create resource
Namespace/velero: created
ClusterRoleBinding/velero: attempting to create resource
ClusterRoleBinding/velero: already exists, proceeding
ClusterRoleBinding/velero: created
ServiceAccount/velero: attempting to create resource
ServiceAccount/velero: created
Secret/cloud-credentials: attempting to create resource
Secret/cloud-credentials: created
BackupStorageLocation/default: attempting to create resource
BackupStorageLocation/default: created
VolumeSnapshotLocation/default: attempting to create resource
VolumeSnapshotLocation/default: created
Deployment/velero: attempting to create resource
An error occurred:
Error installing Velero. Use kubectl logs deploy/velero -n velero to
check the deploy logs: Error creating resource Deployment/velero: the
server could not find the requested resource
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2279?email_source=notifications&email_token=ALNFFOSJRFLAS6S5XFORP5TREDWWDA5CNFSM4KWNBHCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMU3WIQ#issuecomment-589937442>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALNFFOTOC5BDIXAQXNRNA7DREDWWDANCNFSM4KWNBHCA>
.
|
|
@stalinbritto glad you got it working. The error is likely because v1.0.0 used the Closing this out as resolved. |
|
I got same error with GCP experimental k8 cluster, Error installing Velero. Use kubectl logs deploy/velero -n velero to check the deploy logs: Error creating resource Deployment/velero: the server could not find the requested resource then I deleted that I created a normal cluster it is working now. |
What steps did you take and what happened:
[A clear and concise description of what the bug is, and what commands you ran.)
What did you expect to happen:
The output of the following commands will help us better understand what's going on:
(Pasting long output into a GitHub gist or other pastebin is fine.)
kubectl logs deployment/velero -n velerovelero backup describe <backupname>orkubectl get backup/<backupname> -n velero -o yamlvelero backup logs <backupname>velero restore describe <restorename>orkubectl get restore/<restorename> -n velero -o yamlvelero restore logs <restorename>Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
velero version): 1.0.0velero client config get features): aws and azure cloudkubectl version): 1.16/etc/os-release): Ubuntu 16Can you please suggest what i missed ?.
The text was updated successfully, but these errors were encountered: