Skip to content

[WIP] Introduce node capabilities reporting and inferencing framework #133389

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.

Sign up for GitHub

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

Jump to bottom
Draft
wants to merge 6 commits into
base: master
Choose a base branch
from
Draft

[WIP] Introduce node capabilities reporting and inferencing framework #133389

wants to merge 6 commits into from

Conversation

pravk03
Copy link
Contributor

@pravk03 pravk03 commented Aug 5, 2025

What type of PR is this?

/kind feature
/kind api-change

What this PR does / why we need it:

This PR introduces the initial draft implementation for KEP-5328

Which issue(s) this PR is related to:

KEP: kubernetes/enhancements#5347

Special notes for your reviewer:

Does this PR introduce a user-facing change?

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

@k8s-ci-robot
Copy link
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.

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 do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. kind/feature Categorizes issue or PR as related to a new feature. 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/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 5, 2025
@k8s-ci-robot
Copy link
Contributor

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 k8s-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Aug 5, 2025
@k8s-ci-robot
Copy link
Contributor

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

@k8s-ci-robot k8s-ci-robot requested review from AxeZhan and dims August 5, 2025 18:57
@k8s-ci-robot k8s-ci-robot added area/kubelet sig/apps Categorizes an issue or PR as relevant to SIG Apps. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Aug 5, 2025
@github-project-automation github-project-automation bot moved this to Needs Triage in SIG Apps Aug 5, 2025
@pravk03 pravk03 changed the title Introduce node capabilities reporting and inferencing framework [WIP] Introduce node capabilities reporting and inferencing framework Aug 5, 2025
@ffromani
Copy link
Contributor

ffromani commented Aug 6, 2025

/cc

@k8s-ci-robot k8s-ci-robot requested a review from ffromani August 6, 2025 17:19
@ffromani
Copy link
Contributor

ffromani commented Aug 6, 2025

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Aug 6, 2025
@pravk03 pravk03 force-pushed the node-capabilities branch from de30a93 to 1d15b3a Compare August 7, 2025 00:28
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

The full list of commands accepted by this bot can be found 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

@pravk03 pravk03 force-pushed the node-capabilities branch 2 times, most recently from 02d0205 to 24b7efe Compare August 7, 2025 16:25
@pravk03
Copy link
Contributor Author

pravk03 commented Aug 7, 2025

/ok-to-test

@pravk03 pravk03 force-pushed the node-capabilities branch from 24b7efe to 389b6cc Compare August 8, 2025 01:26
@bart0sh bart0sh moved this from Triage to Work in progress in SIG Node: code and documentation PRs Aug 8, 2025
@pravk03 pravk03 force-pushed the node-capabilities branch from 389b6cc to 01c8d35 Compare August 11, 2025 19:17
@pravk03
Copy link
Contributor Author

pravk03 commented Aug 11, 2025

/ok-to-test

@pravk03 pravk03 force-pushed the node-capabilities branch from 01c8d35 to 9cfa56f Compare August 11, 2025 20:17
@pravk03
Copy link
Contributor Author

pravk03 commented Aug 11, 2025

/ok-to-test

@pravk03
Copy link
Contributor Author

pravk03 commented Aug 11, 2025

/cc @tallclair

@k8s-ci-robot k8s-ci-robot requested a review from tallclair August 11, 2025 20:37
@k8s-ci-robot
Copy link
Contributor

@pravk03: 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-kubernetes-unit 9cfa56f link true /test pull-kubernetes-unit
pull-kubernetes-unit-windows-master 9cfa56f link false /test pull-kubernetes-unit-windows-master
pull-kubernetes-e2e-gce 9cfa56f link true /test pull-kubernetes-e2e-gce
pull-kubernetes-verify 9cfa56f link true /test pull-kubernetes-verify

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.

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

@AxeZhan AxeZhan Awaiting requested review from AxeZhan

@dims dims Awaiting requested review from dims

@ffromani ffromani Awaiting requested review from ffromani

@tallclair tallclair Awaiting requested review from tallclair

Assignees
No one assigned
Labels
area/kubelet cncf-cla: yes Indicates the PR's author has 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. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API kind/feature Categorizes issue or PR as related to a new feature. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. sig/apps Categorizes an issue or PR as relevant to SIG Apps. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
SIG Apps
Status: Needs Triage
SIG Node: code and documentation PRs
Status: Work in progress
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@pravk03 @k8s-ci-robot @ffromani