<p>I am following <a href="https://medium.com/@maheshd7878/restore-backup-migrate-kubernetes-cluster-with-velero-434fa151f1e8" rel="nofollow noreferrer">this tutorial</a> to install Velero to backup my cluster.</p>
<p>I have successfully installed the Minio the deployment but I am encountering a problem when installing Velero itself.</p>
<p>When I run the command:</p>
<pre><code>    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=&quot;true&quot;,s3Url=http://minio.velero.svc:9000
</code></pre>
<p>I keep getting this error:</p>
<pre><code>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
</code></pre>
<p>When I type the <code>kubectl logs</code> command, I get this:</p>
<pre><code>ubuntu@kubemaster:~$ kubectl logs deploy/velero -n velero
Error from server (NotFound): deployments.apps &quot;velero&quot; not found
</code></pre>
<p>Am I missed something?</p>

joe1531
<p>In the article you mentioned you fetch and install <code>minio 1.1.0</code> version.</p>
<pre><code>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/
</code></pre>
<p>At the same time you use aws plugin in command <code>--plugins velero/velero-plugin-for-aws:v1.0.0</code></p>
<hr />
<p>As per <a href="https://github.com/vmware-tanzu/velero/issues/2572#issuecomment-638269556" rel="nofollow noreferrer">comment</a> in <a href="https://github.com/vmware-tanzu/velero/issues/2572#" rel="nofollow noreferrer">Error in creating CRD on openshift 3.11</a>:</p>
<blockquote>
<p>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: <a href="https://velero.io/docs/v1.1.0/aws-config/" rel="nofollow noreferrer">https://velero.io/docs/v1.1.0/aws-config/</a></p>
</blockquote>
<p>By opening documentation for 1.1.0 aws configuration you see that no plugin argument was used in <code>velero install</code> command (by the way in medium article also).</p>
<pre><code>velero install \
    --provider aws \
    --bucket $BUCKET \
    --secret-file ./credentials-velero \
    --backup-location-config region=$REGION \
    --snapshot-location-config region=$REGION
</code></pre>
<p>So it could be version issue. Think you should either use newer <a href="https://github.com/vmware-tanzu/velero/tags" rel="nofollow noreferrer">velero versions</a> either configure aws without plugin according to old documentation.</p>
