Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure: skip non azure nodes #6291

Merged
merged 1 commit into from
Jan 3, 2024

Conversation

sergelogvinov
Copy link
Contributor

What type of PR is this?

/kind feature

What this PR does / why we need it:

Skip non azure nodes (providerID) to support on-premise kubernetes nodes.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

If kubernetes cluster has non azure node, node-autoscaller wouldn't start.

Azure Cloud is highly compatible with hybrid cloud environments,
This feature facilitates the seamless integration of on-premise infrastructure with Azure Cloud.

Does this PR introduce a user-facing change?


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


Skip non azure providerID to support on-premise kubernetes nodes.
@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. area/provider/azure Issues or PRs related to azure provider labels Nov 16, 2023
@k8s-ci-robot k8s-ci-robot added area/cluster-autoscaler size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Nov 16, 2023
Copy link
Member

@Bryce-Soghigian Bryce-Soghigian left a comment

Choose a reason for hiding this comment

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

How does this work for kubemark and other non azure nodes? I guess we just skip?

@sergelogvinov
Copy link
Contributor Author

How does this work for kubemark and other non azure nodes? I guess we just skip?

Yep, otherwise it will stack on booting process (creating node groups).
It's the same as you use node auto discovery labels. All unlabeled nodes or kubernetes.azure.com/managed=false should be skipped.

@x13n
Copy link
Member

x13n commented Dec 28, 2023

/assign @feiskyer

@feiskyer
Copy link
Member

feiskyer commented Jan 3, 2024

looks reasonable for hybrid cluster.
/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 3, 2024
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Bryce-Soghigian, feiskyer, sergelogvinov

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:

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 the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 3, 2024
@k8s-ci-robot k8s-ci-robot merged commit f4891e3 into kubernetes:master Jan 3, 2024
6 checks passed
@sergelogvinov sergelogvinov deleted the non-azure-providerid branch January 3, 2024 04:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/cluster-autoscaler area/provider/azure Issues or PRs related to azure provider cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants