Promote cluster-proportional-autoscaler:v1.10.1 images.

[MrHohn]

Ref:

• Can't use mutil targets on helm chart kubernetes-sigs/cluster-proportional-autoscaler#248.
• Node scale up triggers deployment changes before Nodes get ready kubernetes-sigs/cluster-proportional-autoscaler#255

We are releasing a new version of cluster-proportional-autoscaler that:

1. Contains support for multi-targets.
2. Fixes a bug where not ready nodes were included when making scaling decision.

Release tag: https://github.com/kubernetes-sigs/cluster-proportional-autoscaler/releases/tag/v1.10.1

cc @gchaviaras-NS1 @johnitvn @kokes

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: MrHohn

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:

• registry.k8s.io/images/k8s-staging-cpa/OWNERS [MrHohn]

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

[MrHohn]

PR had been updated to promote images for v1.10.1 instead (including a new bug fix).

[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