chore: update cdi.go

[eltociear]

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

charcter -> character

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: eltociear Once this PR has been reviewed and has the lgtm label, please assign kwiesmueller for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files: - **[vertical-pod-autoscaler/OWNERS](https://github.com/kubernetes/autoscaler/blob/master/vertical-pod-autoscaler/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[k8s-ci-robot]

Hi @eltociear. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[Shubham82]

@eltociear, IMO we can't change the vendor directory, these dependencies are mostly coming from the k/k repo and are updated from there, this package has not been updated there yet https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/cm/util/cdi/cdi.go#L119

Once upstream is updated, then we can upgrade the VPA vendor directory.

[Shubham82]

cc @kwiesmueller @voelzmo PTAL!

[adrianmoisey]

Out of curiosity, what is the process to get a vendor directory updated? Is it this script: https://github.com/kubernetes/autoscaler/blob/master/vertical-pod-autoscaler/hack/update-kubernetes-deps.sh

[Shubham82]

Out of curiosity, what is the process to get a vendor directory updated? Is it this script: https://github.com/kubernetes/autoscaler/blob/master/vertical-pod-autoscaler/hack/update-kubernetes-deps.sh

IMO the script you mentioned above is updating the VPA vendor directory The script for updating the VPA e2e vendor directory is as follows: https://github.com/kubernetes/autoscaler/blob/master/vertical-pod-autoscaler/hack/update-kubernetes-deps-in-e2e.sh

[Shubham82]

Out of curiosity, what is the process to get a vendor directory updated?

The purpose is to update/sync VPA dependencies corresponding to upstream repositories`.