Skip to content

Oci fix virtual node skip release 1.32#9474

Open
shreyshj wants to merge 1 commit intokubernetes:cluster-autoscaler-release-1.32from
shreyshj:oci-fix-virtual-node-skip-release-1.32
Open

Oci fix virtual node skip release 1.32#9474
shreyshj wants to merge 1 commit intokubernetes:cluster-autoscaler-release-1.32from
shreyshj:oci-fix-virtual-node-skip-release-1.32

Conversation

@shreyshj
Copy link
Copy Markdown

What type of PR is this?

/kind bug

What this PR does / why we need it:

This PR backports a fix for OCI clusters with mixed node types (managed nodes + virtual nodes).

Today, Cluster Autoscaler looks for the oci.oraclecloud.com/node-pool-id annotation on all non-self-managed nodes to determine the node pool a node belongs to. This breaks for virtual nodes, because virtual nodes do not have this annotation.

This change fixes that behavior by skipping virtual nodes during node pool identification, allowing Cluster Autoscaler to work correctly on mixed node clusters.

We need this in the release branch so updated images can be included in the April release, instead of shipping only the security-patched images without this fix.

Which issue(s) this PR fixes:

Fixes #NONE

Special notes for your reviewer:

This is a backport of an already merged fix for the OCI cloudprovider.

Customer impact:

  • OCI Media Services is currently blocked from using Cluster Autoscaler on mixed node clusters because virtual nodes do not carry the oci.oraclecloud.com/node-pool-id annotation.

Does this PR introduce a user-facing change?

OCI Cluster Autoscaler now skips virtual nodes when resolving node pool IDs in mixed managed-node and virtual-node clusters, fixing autoscaler support for this configuration.

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. 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-area needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Apr 10, 2026
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

Welcome @shreyshj!

It looks like this is your first PR to kubernetes/autoscaler 🎉. 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/autoscaler 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 k8s-ci-robot added area/cluster-autoscaler needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. area/provider/alicloud Issues or PRs related to the AliCloud cloud provider implementation labels Apr 10, 2026
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

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

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.

@k8s-ci-robot k8s-ci-robot added area/provider/aws Issues or PRs related to aws provider area/provider/azure Issues or PRs related to azure provider and removed do-not-merge/needs-area labels Apr 10, 2026
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: shreyshj
Once this PR has been reviewed and has the lgtm label, please assign towca 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

@k8s-ci-robot k8s-ci-robot added area/provider/cluster-api Issues or PRs related to Cluster API provider area/provider/gce labels Apr 10, 2026
@linux-foundation-easycla
Copy link
Copy Markdown

CLA Not Signed

@k8s-ci-robot k8s-ci-robot added area/provider/hetzner Issues or PRs related to Hetzner provider area/provider/oci Issues or PRs related to oci provider size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Apr 10, 2026
@shreyshj shreyshj changed the base branch from master to cluster-autoscaler-release-1.32 April 10, 2026 14:03
@k8s-ci-robot k8s-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Apr 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/cluster-autoscaler area/provider/alicloud Issues or PRs related to the AliCloud cloud provider implementation area/provider/aws Issues or PRs related to aws provider area/provider/azure Issues or PRs related to azure provider area/provider/cluster-api Issues or PRs related to Cluster API provider area/provider/gce area/provider/hetzner Issues or PRs related to Hetzner provider area/provider/oci Issues or PRs related to oci provider cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. kind/bug Categorizes issue or PR as related to a bug. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants