Change VPA storage version from v1beta2 to v1

[bskiba]

With the recent switch to generated CRD definition, we also stopped saving unknown fields. Since v1beta2 does not contain some fields that v1 does, the fields get dropped silently on object creation.
Switching to v1 as storage version solves that problem.

fixes #3800

[bskiba]

@jbartosik @krzysied Could one of you review?

[bskiba]

I think this will also fix the failing e2e test - Admission-controller keeps limits unchanged when container controlled values is requests only (https://k8s-testgrid.appspot.com/sig-autoscaling-vpa#autoscaling-vpa-admission-controller).

controlledValues is also missing from v1beta2 and thus dropped.

[jbartosik]

I don't see any problems but I have a question.

How does one update an existing cluster (and preserve existing VPAs and checkpoints)?

[bskiba]

When you apply the api changes, the api server will perform conversion of the stored objects whenever the object is read or written. Our conversion is a noop, since all the existing fields are the same between versions. This is true for both vpas and vpacheckpoints.

[jbartosik]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bskiba, jbartosik

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• vertical-pod-autoscaler/OWNERS [bskiba,jbartosik]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment