update CCM image to v32.2.3 #130696

YifeiZhuang · 2025-03-10T18:40:52Z

What type of PR is this?

update the test image for CCM component, new image is available

gcr.io/k8s-staging-cloud-provider-gcp/cloud-controller-manager:v32.2.3

From new CCM release https://github.com/kubernetes/cloud-provider-gcp/releases/tag/ccm%2Fv32.2.3

/kind cleanup
/kind failing-test
/kind flake

What this PR does / why we need it:

update the test image for CCM component, new image is available

gcr.io/k8s-staging-cloud-provider-gcp/cloud-controller-manager:v32.2.3

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

No.

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

https://github.com/kubernetes/cloud-provider-gcp/blob/master/docs/RELEASE.md#update-gce-job-version

/assign aojea
/assign mmamczur

k8s-ci-robot · 2025-03-10T18:41:00Z

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

k8s-ci-robot · 2025-03-10T18:41:00Z

Welcome @YifeiZhuang!

It looks like this is your first PR to kubernetes/kubernetes 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kubernetes has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

k8s-ci-robot · 2025-03-10T18:41:01Z

Hi @YifeiZhuang. Thanks for your PR.

I'm waiting for a kubernetes 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.

YifeiZhuang · 2025-03-10T19:55:24Z

/assign aojea
/assign mmamczur

YifeiZhuang · 2025-03-12T21:24:34Z

@aojea reminder please approve the PR. It looks mmamczur@ is not in the review/approval list here.
ref:

kubernetes/cluster/OWNERS

Line 7 in 8456726

- aojea

aojea · 2025-03-12T22:50:45Z

/ok-to-test
/lgtm
/approve

Thanks

k8s-ci-robot · 2025-03-12T22:50:51Z

LGTM label has been added.

Git tree hash: b9b9d478b97cbfc74a4af79f0bcf113fbc1e53ef

k8s-ci-robot · 2025-03-12T22:50:56Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aojea, YifeiZhuang

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:

~~cluster/gce/manifests/OWNERS~~ [aojea]

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

YifeiZhuang · 2025-03-13T00:05:33Z

/test pull-kubernetes-e2e-gce

"no ready nodes", seem not new, not sure if it's flakiness or real issue.

Waiting for 4 ready nodes. 0 ready nodes, 4 registered. Retrying.
Detected 0 ready nodes, found 4 nodes out of expected 4. Your cluster may not be fully functional.

pacoxu · 2025-03-13T01:48:05Z

/hold
the CI keeps failing

Mar 13 00:50:08.077744 bootstrap-e2e-master kubelet[9480]: I0313 00:50:08.077711    9480 event.go:389] "Event occurred" object="kube-system/cloud-controller-manager-bootstrap-e2e-master" fieldPath="spec.containers{cloud-controller-manager}" kind="Pod" apiVersion="v1" type="Warning" reason="BackOff" message="Back-off restarting failed container cloud-controller-manager in pod cloud-controller-manager-bootstrap-e2e-master_kube-system(cfc4e3b5c5aff2b5a7fedd060d12b5f1)"

From kueblet log, we can see the cloud-controller-manager cannot start correctly after updating the image. https://storage.googleapis.com/kubernetes-ci-logs/pr-logs/pull/130696/pull-kubernetes-e2e-gce/1899975142994350080/artifacts/bootstrap-e2e-master/kubelet.log

aojea · 2025-03-13T09:45:45Z

/hold

image seems to be wrong

mmamczur · 2025-03-13T10:14:46Z

the binary is not in the expected path

aojea · 2025-05-09T08:43:27Z

/retest

k8s-ci-robot · 2025-05-09T09:38:01Z

@YifeiZhuang: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kubernetes-e2e-gce	`3a4b505`	link	true	`/test pull-kubernetes-e2e-gce`

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

aojea · 2025-05-09T10:57:54Z

cluster/gce/manifests/cloud-controller-manager.manifest

@@ -23,7 +23,7 @@
 "containers":[
    {
    "name": "cloud-controller-manager",
-    "image": "gcr.io/k8s-staging-cloud-provider-gcp/cloud-controller-manager:v30.0.0",
+    "image": "gcr.io/k8s-staging-cloud-provider-gcp/cloud-controller-manager:v32.2.3",


@YifeiZhuang can you please switch to the latest 33.0.0?

https://github.com/kubernetes/cloud-provider-gcp/releases/tag/ccm%2Fv33.0.0

I had a separate PR to address this: #132515

update CCM iamge to v32.2.3

3a4b505

k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Mar 10, 2025

k8s-ci-robot requested review from marseel and MrHohn March 10, 2025 18:41

k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Mar 10, 2025

k8s-ci-robot assigned aojea and mmamczur Mar 10, 2025

YifeiZhuang changed the title ~~update CCM iamge to v32.2.3~~ update CCM image to v32.2.3 Mar 10, 2025

k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. lgtm "Looks good to me", indicates that a PR is ready to be merged. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Mar 12, 2025

k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 12, 2025

k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 13, 2025

YifeiZhuang mentioned this pull request Mar 13, 2025

32.2.3 image seems broken kubernetes/cloud-provider-gcp#821

Open

aojea reviewed May 9, 2025

View reviewed changes

gavinkflam mentioned this pull request Jun 12, 2025

bug: Fix misleading response codes in admission control metrics #132165

Merged

This was referenced Jun 24, 2025

Image registry.k8s.io/cloud-provider-gcp/cloud-controller-manager:v30.1.0 is missing kubernetes/cloud-provider-gcp#769

Open

Update CCM image to v33.0.0 #132515

Open

update CCM image to v32.2.3 #130696

Are you sure you want to change the base?

update CCM image to v32.2.3 #130696

Conversation

YifeiZhuang commented Mar 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

Uh oh!

k8s-ci-robot commented Mar 10, 2025

Uh oh!

k8s-ci-robot commented Mar 10, 2025

Uh oh!

k8s-ci-robot commented Mar 10, 2025

Uh oh!

YifeiZhuang commented Mar 10, 2025

Uh oh!

YifeiZhuang commented Mar 12, 2025

Uh oh!

aojea commented Mar 12, 2025

Uh oh!

k8s-ci-robot commented Mar 12, 2025

Uh oh!

k8s-ci-robot commented Mar 12, 2025

Uh oh!

YifeiZhuang commented Mar 13, 2025

Uh oh!

pacoxu commented Mar 13, 2025

Uh oh!

aojea commented Mar 13, 2025

Uh oh!

mmamczur commented Mar 13, 2025

Uh oh!

aojea commented May 9, 2025

Uh oh!

k8s-ci-robot commented May 9, 2025

Uh oh!

aojea May 9, 2025

Choose a reason for hiding this comment

Uh oh!

gemmahou Jun 24, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

YifeiZhuang commented Mar 10, 2025 •

edited

Loading