[dep] Updated k8s.io/autoscaler/cluster-autoscaler version to a stable one.

[trasc]

What would you like to be cleaned:

Use a released version of k8s.io/autoscaler/cluster-autoscaler containing kubernetes/autoscaler@5155725

Why is this needed:

Have clean dependencies.

[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

[tenzen-y]

/remove-lifecycle stale

@trasc Since released the new cluster-autoscaler with PriviosningRequest API, we can do this, right?

[trasc]

@tenzen-y Indeed the the code we need is now part of a github release 1.29.0 but unfortunately the release is tagged with cluster-autoscaler-1.29.0 instead of cluster-autoscaler/v1.29.0 and it cannot be referenced from go.mod.

[tenzen-y]

@tenzen-y Indeed the the code we need is now part of a github release 1.29.0 but unfortunately the release is tagged with cluster-autoscaler-1.29.0 instead of cluster-autoscaler/v1.29.0 and it cannot be referenced from go.mod.

@trasc Yea, that makes sense. Indeed, I'm working on new tag format k8s.io/autoscaler/cluster-autoscaler/apis in kubernetes/autoscaler#6315 (comment).

[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

[tenzen-y]

/remove-lifecycle stale

[tenzen-y]

This is replaced with #1896
/close

[k8s-ci-robot]

@tenzen-y: Closing this issue.

In response to this:

This is replaced with #1896
/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.