Kubernetes 在k8群集上安装Velero备份失败

Kubernetes 在k8群集上安装Velero备份失败,kubernetes,backup,velero,Kubernetes,Backup,Velero,我试图在Kubernestes集群上安装Velero进行备份,安装了Minio,可以访问,并创建了一个bucket,即kubedemo。Velero已下载,路径已设置,运行正常,但当我点击安装命令时,日志文件中出现“给我”错误 [root@kube-master ~]# velero version Client: Version: v1.0.0 Git commit: 72f5cadc3a865019ab9dc043d4952c9bfd5f2ecb <er

我试图在Kubernestes集群上安装Velero进行备份,安装了Minio,可以访问,并创建了一个bucket,即kubedemo。Velero已下载,路径已设置,运行正常,但当我点击安装命令时,日志文件中出现“给我”错误

[root@kube-master ~]# velero version
Client:
        Version: v1.0.0
        Git commit: 72f5cadc3a865019ab9dc043d4952c9bfd5f2ecb
<error getting server version: namespaces "velero" not found>


[root@kube-master ~]# velero install --provider aws --bucket kubedemo --secret-file ./minio.credentials --use-restic --backup-location-config region=minio,s3ForcePathStyle=true,s3Url=http://192.x.x.x:9000
    CustomResourceDefinition/downloadrequests.velero.io: attempting to create resource
    CustomResourceDefinition/downloadrequests.velero.io: already exists, proceeding
    CustomResourceDefinition/downloadrequests.velero.io: created
    CustomResourceDefinition/deletebackuprequests.velero.io: attempting to create resource
    CustomResourceDefinition/deletebackuprequests.velero.io: already exists, proceeding
    CustomResourceDefinition/deletebackuprequests.velero.io: created
    CustomResourceDefinition/resticrepositories.velero.io: attempting to create resource
    CustomResourceDefinition/resticrepositories.velero.io: already exists, proceeding
    CustomResourceDefinition/resticrepositories.velero.io: created
    CustomResourceDefinition/volumesnapshotlocations.velero.io: attempting to create resource
    CustomResourceDefinition/volumesnapshotlocations.velero.io: already exists, proceeding
    CustomResourceDefinition/volumesnapshotlocations.velero.io: created
    CustomResourceDefinition/serverstatusrequests.velero.io: attempting to create resource
    CustomResourceDefinition/serverstatusrequests.velero.io: already exists, proceeding
    CustomResourceDefinition/serverstatusrequests.velero.io: created
    CustomResourceDefinition/backups.velero.io: attempting to create resource
    CustomResourceDefinition/backups.velero.io: already exists, proceeding
    CustomResourceDefinition/backups.velero.io: created
    CustomResourceDefinition/restores.velero.io: attempting to create resource
    CustomResourceDefinition/restores.velero.io: already exists, proceeding
    CustomResourceDefinition/restores.velero.io: created
    CustomResourceDefinition/schedules.velero.io: attempting to create resource
    CustomResourceDefinition/schedules.velero.io: already exists, proceeding
    CustomResourceDefinition/schedules.velero.io: created
    CustomResourceDefinition/podvolumebackups.velero.io: attempting to create resource
    CustomResourceDefinition/podvolumebackups.velero.io: already exists, proceeding
    CustomResourceDefinition/podvolumebackups.velero.io: created
    CustomResourceDefinition/podvolumerestores.velero.io: attempting to create resource
    CustomResourceDefinition/podvolumerestores.velero.io: already exists, proceeding
    CustomResourceDefinition/podvolumerestores.velero.io: created
    CustomResourceDefinition/backupstoragelocations.velero.io: attempting to create resource
    CustomResourceDefinition/backupstoragelocations.velero.io: already exists, proceeding
    CustomResourceDefinition/backupstoragelocations.velero.io: created
    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: 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
    [root@kube-master ~]# kubectl logs deploy/velero -n velero
    Error from server (NotFound): deployments.apps "velero" not found

您缺少必需的参数
--插件velero/velero aws插件:v1.0.0

缺少所需参数

--插件velero/velero aws插件:v1.0.0

您使用的是
GCP的实验性k8集群吗?因为我得到了同样的错误,后来我切换到
正常集群

你使用的是
GCP的实验性k8集群
?因为我遇到了同样的错误,后来我切换到
普通集群

kubectl logs deploy/velero-n velero告诉你什么?@hizzy谢谢,我刚刚使用了对我有用的go语言脚本kubectl logs deploy/velero-n velero告诉你什么?@hizzy谢谢,我刚刚使用了适合我的go语言脚本#Sharma我正在我的barematel环境中运行它#Sharma我在我的barematel环境中运行它。您是如何解决这个问题的?您是否遇到这样的错误?部署/velero:尝试创建资源发生错误:请重新措辞以减少询问问题的印象。#Sharma我在我的barematel环境中运行它环境您是如何解决这个问题的?您是否遇到这样的错误?部署/velero:尝试创建资源发生错误:请重新措辞以减少提问的印象。--插件velero/velero-plugin for aws:v1.0.0它为meThis工作,如果解决了问题,则应将其标记为正确答案。此标志是告诉Velero要安装的插件所必需的,OP的install命令中缺少此标志。它肯定会导致部署失败。--插件velero/velero-plugin for aws:v1.0.0它为meThis工作过,如果它解决了问题,应该将其标记为正确答案。此标志是告诉Velero要安装的插件所必需的,OP的install命令中缺少此标志。它肯定会导致部署失败。
[root@kube-master ~]# cat minio.credentials
[default]
aws_access_key_id=minioadmin
aws_secret_access_key=minioadmin