Velero not working without Kubernetes metrics Server

What steps did you take and what happened:

velero not able to discover the custom.metrics.k8s.io/v1beta1 evel=warning msg="Failed to discover group: custom.metrics.k8s.io/v1beta1" error="the server is currently unable to handle the request" logSource="pkg/discovery/helper.go:154"

What did you expect to happen:

Velero to do proper backups without any errors, as metrics were disabled using helm chart installatio

Anything else you would like to add:

Why does velero expect kubernetes metrics server to be running if metrics are disabled anyways? Is this a hard requirement for velero backups to happen?

Environment:

Velero version (use velero version): 1.5.2
Velero features (use velero client config get features):
Kubernetes version (use kubectl version): 1.16
Kubernetes installer & version:
Cloud provider or hardware configuration: aws
OS (e.g. from /etc/os-release):

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

:+1: for "I would like to see this bug fixed as soon as possible"
:-1: for "There are more important bugs to focus on right now"

vmware-tanzu / velero

Velero not working without Kubernetes metrics Server #3472

WARNING: the client version does not match the server version. Please update server