Skip to content

Promote PodLevelResources to Beta#132999

Merged
k8s-ci-robot merged 1 commit intokubernetes:masterfrom
ndixita:pod-level-resources-beta
Jul 30, 2025
Merged

Promote PodLevelResources to Beta#132999
k8s-ci-robot merged 1 commit intokubernetes:masterfrom
ndixita:pod-level-resources-beta

Conversation

@ndixita
Copy link
Copy Markdown
Contributor

@ndixita ndixita commented Jul 16, 2025

What type of PR is this?

What this PR does / why we need it:

Graduate PodLevelResources feature to beta / on by default.

Which issue(s) this PR is related to:

kubernetes/enhancements#2837

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Graduate `PodLevelResources` feature to beta and have it on by default. This feature allows defining CPU and memory resources for an entire pod in `pod.spec.resources`.

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

- [KEP]: - [KEP]: https://kep.k8s.io/2837

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@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. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. 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 Jul 16, 2025
@k8s-ci-robot
Copy link
Copy Markdown
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.

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 the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Jul 16, 2025
@ndixita ndixita marked this pull request as ready for review July 16, 2025 19:21
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 16, 2025
@k8s-ci-robot k8s-ci-robot requested review from mrunalp and thockin July 16, 2025 19:21
@ndixita ndixita moved this to Needs Review in SIG Node: Pod Level Resources Jul 16, 2025
@ndixita ndixita force-pushed the pod-level-resources-beta branch from 3e5e00e to c4e26d6 Compare July 16, 2025 21:03
Comment thread pkg/features/kube_features.go Outdated
Comment thread test/compatibility_lifecycle/reference/versioned_feature_list.yaml Outdated
@k8s-ci-robot k8s-ci-robot added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Jul 22, 2025
@pacoxu
Copy link
Copy Markdown
Member

pacoxu commented Jul 24, 2025

/sig node
/kind feature

BTW, Please run 'hack/update-featuregates.sh' to update the feature list. to fix the verify-ci failure.

@k8s-ci-robot k8s-ci-robot added sig/node Categorizes an issue or PR as relevant to SIG Node. kind/feature Categorizes issue or PR as related to a new feature. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Jul 24, 2025
@ndixita ndixita force-pushed the pod-level-resources-beta branch from 9e2ba2f to bf3b6cd Compare July 24, 2025 19:28
@ndixita
Copy link
Copy Markdown
Contributor Author

ndixita commented Jul 24, 2025

/test pull-kubernetes-e2e-gce

@ndixita
Copy link
Copy Markdown
Contributor Author

ndixita commented Jul 25, 2025

/assign @dchen1107

The feature gate to be promoted to beta only after #133279 and #132430 are approved/merged.

@jenshu
Copy link
Copy Markdown
Contributor

jenshu commented Jul 29, 2025

/milestone v1.34

@ndixita
Copy link
Copy Markdown
Contributor Author

ndixita commented Jul 29, 2025

/assign @tallclair

@dchen1107
Copy link
Copy Markdown
Member

Discussed this at SIG Node weekly earlier today and agreed the last blocker for beta is #133279, which is approved and waiting for the merge.

/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 Jul 29, 2025
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

LGTM label has been added.

DetailsGit tree hash: f33e81d0d846c6f0c758af77f648f44e94a2b40c

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dchen1107, ndixita

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

The pull request process is described 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 the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 29, 2025
@k8s-ci-robot k8s-ci-robot merged commit 3e3b244 into kubernetes:master Jul 30, 2025
15 checks passed
@github-project-automation github-project-automation Bot moved this from Needs Review to Done in SIG Node: Pod Level Resources Jul 30, 2025
choejwoo pushed a commit to choejwoo/kubernetes that referenced this pull request Aug 8, 2025
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. 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. 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. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/node Categorizes an issue or PR as relevant to SIG Node. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

8 participants