Skip to content

Adopt NodeLifecycleControllerOptions for k8s.io/cloud-provider v0.37.0 - #10777

Open
danbruno101 wants to merge 1 commit into
kubernetes-sigs:masterfrom
danbruno101:fix/node-monitor-period-1.37
Open

Adopt NodeLifecycleControllerOptions for k8s.io/cloud-provider v0.37.0#10777
danbruno101 wants to merge 1 commit into
kubernetes-sigs:masterfrom
danbruno101:fix/node-monitor-period-1.37

Conversation

@danbruno101

@danbruno101 danbruno101 commented Jul 31, 2026

Copy link
Copy Markdown

What type of PR is this?
/kind bug

What this PR does / why we need it:
Prepares this repo for the k8s.io/* v0.37.0 dependency bump. kubernetes/kubernetes#137964
moved NodeMonitorPeriod from KubeCloudSharedConfiguration to a new
NodeLifecycleControllerConfiguration and added a concurrentNodeLifecycleSyncs parameter
to NewCloudNodeLifecycleController. This updates both call sites: the standard CCM node
lifecycle controller starter and the GKE tenant controller manager. Compile fix only;
no behavioral change at default flag values.

Which issue(s) this PR fixes:
Fixes #1254

Special notes for your reviewer:
CI is expected to fail until the dependency bump to k8s.io/* v0.37.0 lands — this change
is source-compatible with v0.37.0 only. Note the staging pins live in the replace blocks
of both go.mod and go.work; this PR intentionally touches neither and contains only the
two source fixes, to compose with the bump PR. Verified against
k8s.io/cloud-provider@master (go build ./cmd/... passes with the vendor tree synced).
Opened per elmiko's suggestion so the provider team can sequence it with the bump.
Happy to rebase or fold into the bump PR as preferred.

Does this PR introduce a user-facing change?

NONE

kubernetes/kubernetes#137964 moved NodeMonitorPeriod from
KubeCloudSharedConfiguration to a new NodeLifecycleControllerConfiguration
and added a concurrentNodeLifecycleSyncs parameter to
NewCloudNodeLifecycleController.

Because this repo maintains its own CloudControllerManagerOptions, the new
NodeLifecycleControllerOptions group must be wired into the struct,
constructor, Flags, ApplyTo, and Validate; otherwise --node-monitor-period
would no longer be registered and the controller would receive zero-valued
config. No behavioral change at default flag values. Staged to land with
the v0.37.0 dependency bump.

Signed-off-by: Daniel Bruno <daniel.c.bruno@gmail.com>
@kubernetes-prow kubernetes-prow Bot added do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. do-not-merge/needs-kind labels Jul 31, 2026
@kubernetes-prow

Copy link
Copy Markdown

Welcome @danbruno101!

It looks like this is your first PR to kubernetes-sigs/cloud-provider-azure 🎉. 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-sigs/cloud-provider-azure 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. 😃

@github-actions github-actions Bot added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Jul 31, 2026
@kubernetes-prow

Copy link
Copy Markdown

Hi @danbruno101. 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.

Details

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.

@kubernetes-prow kubernetes-prow Bot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Jul 31, 2026
@kubernetes-prow
kubernetes-prow Bot requested review from JoelSpeed and feiskyer July 31, 2026 14:05
@kubernetes-prow kubernetes-prow Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jul 31, 2026
@kubernetes-prow

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: danbruno101
Once this PR has been reviewed and has the lgtm label, please assign cheftako for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

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

@kubernetes-prow kubernetes-prow Bot 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 Jul 31, 2026
@andyzhangx

Copy link
Copy Markdown
Member

/kind bug
/ok-to-test

@kubernetes-prow kubernetes-prow Bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. kind/bug Categorizes issue or PR as related to a bug. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. do-not-merge/needs-kind labels Jul 31, 2026
@andyzhangx
andyzhangx requested a review from Copilot July 31, 2026 14:39
@kubernetes-prow

Copy link
Copy Markdown

@danbruno101: The following tests 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-cloud-provider-azure-e2e-ccm-vmssflex-capz be300bf link true /test pull-cloud-provider-azure-e2e-ccm-vmssflex-capz
pull-cloud-provider-azure-e2e-ccm-vmss-capz be300bf link true /test pull-cloud-provider-azure-e2e-ccm-vmss-capz
pull-cloud-provider-azure-e2e-ccm-ipv6-vmss-capz be300bf link true /test pull-cloud-provider-azure-e2e-ccm-ipv6-vmss-capz
pull-cloud-provider-azure-e2e-ccm-vmss-multi-slb-capz be300bf link true /test pull-cloud-provider-azure-e2e-ccm-vmss-multi-slb-capz
pull-cloud-provider-azure-e2e-ccm-capz be300bf link true /test pull-cloud-provider-azure-e2e-ccm-capz
pull-cloud-provider-azure-e2e-ccm-dualstack-vmss-capz be300bf link true /test pull-cloud-provider-azure-e2e-ccm-dualstack-vmss-capz
pull-cloud-provider-azure-e2e-ccm-ipv6-capz be300bf link true /test pull-cloud-provider-azure-e2e-ccm-ipv6-capz
pull-cloud-provider-azure-e2e-ccm-dualstack-capz be300bf link true /test pull-cloud-provider-azure-e2e-ccm-dualstack-capz
pull-cloud-provider-azure-e2e-ccm-vmss-ip-lb-capz be300bf link true /test pull-cloud-provider-azure-e2e-ccm-vmss-ip-lb-capz
pull-cloud-provider-azure-e2e-ccm-vmss-shared-probe-capz be300bf link true /test pull-cloud-provider-azure-e2e-ccm-vmss-shared-probe-capz
pull-cloud-provider-azure-e2e-capz be300bf link true /test pull-cloud-provider-azure-e2e-capz
pull-cloud-provider-azure-unit be300bf link true /test pull-cloud-provider-azure-unit

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.

Details

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.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Prepares cloud-provider-azure’s cloud-controller-manager wiring for the upcoming k8s.io/cloud-provider v0.37.0 API changes by introducing NodeLifecycleControllerOptions usage and switching the cloud node lifecycle controller startup path to read NodeMonitorPeriod from the new NodeLifecycleController config (and pass the new concurrency parameter).

Changes:

  • Add NodeLifecycleControllerOptions to CCM options, including flags/apply/validate wiring.
  • Update CCM node lifecycle controller startup to use ComponentConfig.NodeLifecycleController and pass ConcurrentNodeLifecycleSyncs.
  • Update options tests to reflect the config move of NodeMonitorPeriod out of KubeCloudSharedConfiguration.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File Description
cmd/cloud-controller-manager/app/options/options.go Adds NodeLifecycleControllerOptions into CCM option construction, flag sets, apply, and validation.
cmd/cloud-controller-manager/app/options/options_test.go Updates expected option structures for NodeMonitorPeriod relocation and new node lifecycle controller config fields.
cmd/cloud-controller-manager/app/core.go Switches node lifecycle controller startup to the new component config location and passes the new concurrency argument.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants