Verify vendor code in presubmit

[sophieliu15]

Which component are you using?: VPA

Which component hosted in this repository is this a feature for?: All components

Is your feature request designed to solve a problem? If so describe the problem this feature should solve.:
Currently there is no good way to verify the integrity of modules under vendor directory. For example, someone could upgrade go version or go module version; update dependencies; perform go mod vendor; hand edit a go file under vendor and add a new function. The tempered vendor file will be buried in all the vendor changes.

You could look at all the vendor file change and verify individually but it is pretty time consuming and unrealistic.

Describe the solution you'd like.: Add a verification under hack/ directory to verify vendor code integrity. Similar to https://github.com/kubernetes/kubernetes/blob/master/hack/verify-vendor.sh

Describe any alternative solutions you've considered.: Ideally go mod verify should do this but it is not happening: golang/go#27348

Additional context.:

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[Shubham82]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[Shubham82]

Hi @sophieliu15, JFI we removed the Cluster Autoscaler vendor directory in favor of Go modules,
Here is the PR for it: #6572

[Shubham82]

Closing this issue, as it is resolved by the PR #6572
/close

[k8s-ci-robot]

@Shubham82: Closing this issue.

In response to this:

Closing this issue, as it is resolved by the PR #6572
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.