1

I am trying to install Velero for backup on Kubernestes cluster, Minio is installed, accessible and a bucket namely kubedemo is created. Velero is download and path is set, its running fine but When i hit installation command its give me error in log file.

[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

Here is secret file for credential

[root@kube-master ~]# cat minio.credentials
[default]
aws_access_key_id=minioadmin
aws_secret_access_key=minioadmin
muhammad shahan
  • 517
  • 6
  • 17

2 Answers2

3

You are missing the required parameter --plugins velero/velero-plugin-for-aws:v1.0.0

carlisia
  • 138
  • 2
  • 7
Hizzy
  • 741
  • 7
  • 27
  • --plugins velero/velero-plugin-for-aws:v1.0.0 it worked for me – Ashish Karpe Dec 07 '20 at 10:25
  • This should be marked as the correct answer if it solved the issue. This flag is required to tell Velero what plugin to install, and it is missing from the OP's install command. It most definitely would cause the deployment to fail. – carlisia Dec 19 '20 at 17:04
1

Are you using GCP's experimental k8 cluster? Cause I got same error, later I switched to normal cluster.

Hamid Naghipour
  • 3,465
  • 2
  • 26
  • 55