1

I am following this tutorial to install Velero to backup my cluster.

I have successfully installed the Minio the deployment but I am encountering a problem when installing Velero itself.

When I run the command:

    velero install \
--provider aws \
--plugins velero/velero-plugin-for-aws:v1.0.0 \
--bucket velero \
--secret-file ./credentials-velero \
--use-volume-snapshots=false \
--backup-location-config region=minio,s3ForcePathStyle="true",s3Url=http://minio.velero.svc:9000

I keep getting this error:

CustomResourceDefinition/backups.velero.io: 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 CustomResourceDefinition/backups.velero.io: the server could not find the requested resource

When I type the kubectl logs command, I get this:

ubuntu@kubemaster:~$ kubectl logs deploy/velero -n velero
Error from server (NotFound): deployments.apps "velero" not found

Am I missed something?

Wytrzymały Wiktor
  • 11,492
  • 5
  • 29
  • 37
joe1531
  • 345
  • 4
  • 16

1 Answers1

1

In the article you mentioned you fetch and install minio 1.1.0 version.

curl -LO https://github.com/heptio/velero/releases/download/v1.1.0/velero-v1.1.0-linux-amd64.tar.gz
tar -C /usr/local/bin -xzvf velero-v1.1.0-linux-amd64.tar.gz
export PATH=$PATH:/usr/local/bin/velero-v1.1.0-linux-amd64/

At the same time you use aws plugin in command --plugins velero/velero-plugin-for-aws:v1.0.0

As per comment in Error in creating CRD on openshift 3.11:

for v1.1 you don't need to use an external AWS plugin, it was still in-tree. Please make sure you're following the correct docs for the Velero version you're using: https://velero.io/docs/v1.1.0/aws-config/

By opening documentation for 1.1.0 aws configuration you see that no plugin argument was used in velero install command (by the way in medium article also).

velero install \
    --provider aws \
    --bucket $BUCKET \
    --secret-file ./credentials-velero \
    --backup-location-config region=$REGION \
    --snapshot-location-config region=$REGION

So it could be version issue. Think you should either use newer velero versions either configure aws without plugin according to old documentation.

Vit
  • 7,740
  • 15
  • 40
  • Hello @WytrzymałyWiktor. Thank you for your reply. The cluster is currently down so I did not test that yet. As soon as I get it back, I will notify you on how it went when I try modifying the velero version. I tried the newest ones and the oldest ones but still no luck. – joe1531 Nov 25 '21 at 13:27
  • 1
    @WytrzymałyWiktor hello. We decided to not use an on-premises Kubernetes cluster and use Kapsule, which is Scaleway Kubernetes cloud service so I didn't really tried out. Thank you for your answer though – joe1531 Dec 22 '21 at 13:02