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.

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

Document InPlacePodVerticalScalingExclusiveCPUs for v1.32 #48687

Closed
esotsal opened this issue Nov 11, 2024 · 8 comments
Closed

Document InPlacePodVerticalScalingExclusiveCPUs for v1.32 #48687

esotsal opened this issue Nov 11, 2024 · 8 comments
Labels
kind/documentation Categorizes issue or PR as related to documentation. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/docs Categorizes an issue or PR as relevant to SIG Docs. sig/node Categorizes an issue or PR as relevant to SIG Node.
Milestone
1.32

Comments

@esotsal
Copy link

esotsal commented Nov 11, 2024 •
edited by sftim
Loading

This is Support

Hi,

We would like to document InPlacePodVerticalScalingExclusiveCPUs for v1.32 , as suggested here . Can you please help us with this.
@esotsal esotsal added the kind/support Categorizes issue or PR as a support question. label Nov 11, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

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 the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Nov 11, 2024
@esotsal esotsal mentioned this issue Nov 11, 2024
Merged
@sftim
Copy link
Contributor

sftim commented Nov 11, 2024

/remove-kind support
/sig node docs
/kind documentation

@k8s-ci-robot k8s-ci-robot added sig/node Categorizes an issue or PR as relevant to SIG Node. sig/docs Categorizes an issue or PR as relevant to SIG Docs. kind/documentation Categorizes issue or PR as related to documentation. and removed kind/support Categorizes issue or PR as a support question. labels Nov 11, 2024
@sftim
Copy link
Contributor

sftim commented Nov 11, 2024

/milestone 1.32

@k8s-ci-robot k8s-ci-robot added this to the 1.32 milestone Nov 11, 2024
@dipesh-rawat
Copy link
Member

Would this be better tracked under the scope of the existing umbrella issue #48534, as it seems to align with that, or is it better kept separate like this?

@dipesh-rawat
Copy link
Member

Since this is related to documenting feature for the upcoming v1.32 release, please be aware that the Docs freeze is in two weeks on Tuesday 26th November 2024.

@esotsal
Copy link
Author

esotsal commented Nov 13, 2024 •
edited
Loading

Would this be better tracked under the scope of the existing umbrella issue #48534, as it seems to align with that, or is it better kept separate like this?

@tallclair @AnishShah what do you think?

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 11, 2025
@esotsal
Copy link
Author

esotsal commented Feb 16, 2025

Closing as proposed , it is covered in #48534

Milestone should be v1.33

@esotsal esotsal closed this as completed Feb 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/documentation Categorizes issue or PR as related to documentation. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/docs Categorizes an issue or PR as relevant to SIG Docs. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Milestone
1.32
Development

No branches or pull requests
5 participants
@dipesh-rawat @k8s-ci-robot @sftim @k8s-triage-robot @esotsal