cluster-autoscaler: update for svm

[grosser]

What type of PR is this?

/kind bug

What this PR does / why we need it:

for example https://nvd.nist.gov/vuln/detail/CVE-2023-47108

Which issue(s) this PR fixes:

Fixes #6279

SVM updates

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: grosser
Once this PR has been reviewed and has the lgtm label, please assign towca 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:

• cluster-autoscaler/OWNERS

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

[Shubham82]

Thanks @grosser
/lgtm

[Shubham82]

@x13n @BigDarkClown
PTAL!

[Shubham82]

cc @towca @x13n @BigDarkClown
PTAL!

[x13n]

We can merge this, but CA deps are mostly coming from k/k repo and are updated from there on each patch release. I see this package has not been updated there yet: https://github.com/kubernetes/kubernetes/blob/master/go.mod

[x13n]

Actually, this only updates go.mod and doesn't touch vendor, so is really a no-op. Please use update-vendor.sh for dependency updates.

[Shubham82]

/remove-lgtm

[k8s-ci-robot]

PR needs rebase.

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/test-infra repository.

[k8s-triage-robot]

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

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle stale

[k8s-triage-robot]

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

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle rotten

[Shubham82]

Closing this PR, as per the following comment

/close

[k8s-ci-robot]

@Shubham82: Closed this PR.

In response to this:

Closing this PR, as per the following comment

/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.