Update cluster-proportional-autoscaler to v1.9.0

[sathieu]

What type of PR is this?

/kind feature

What this PR does / why we need it:

CVEs

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

Hi @sathieu. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ErikJiang]

/ok-to-test

[tico88612]

/kind feature
/lgtm

[tico88612]

@sathieu Rebase your PR again, because CI has been changed.

[sathieu]

@tico88612 Done

[tico88612]

@sathieu why the ubuntu22-calico-all-in-one-upgrade failed? (not like flaky) Could you fix it?

[sathieu]

The reason is:

message: '0/1 nodes are available: 1 node(s) didn''t match pod anti-affinity rules. preemption: 0/1 nodes are available: 1 node(s) didn''t match pod anti-affinity rules.'
reason: Unschedulable
status: "False"
type: PodScheduled
phase: Pending

There are two pods dns-autoscaler-597dccb9b9-b4wt5 and dns-autoscaler-7b5899494d-j9sct with an antiaffinity rule, and only one node.

[sathieu]

@tico88612 I pushed again, and CI is now passing. Back to you 🏓

[tico88612]

/lgtm

[VannTen]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sathieu, tico88612, VannTen

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:

• OWNERS [VannTen]

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

[tico88612]

@sathieu, how do you fix the CI in your PR? This seems to break the ubuntu22-calico-all-in-one-upgrade job.

[tico88612]

Revert cleanup release-note

/release-note-edit

NONE