Tim Bannister

If you want to transfer this to k/website, we have a Prow command for that (`/transfer website`)

BTW, see https://github.com/kubernetes/autoscaler/issues/6646#issuecomment-2018478351 Feel free to transfer this to k/website. /remove-lifecycle stale

This seems done /close

> We were discussing in the api-machinery triage meeting that there are some issues fitting a pattern like: > > `help-wanted`, `lifecycle/frozen`, `triage/accepted` > > Which are: > > *...

> Please ensure that the issue body includes answers to the following questions: > > - Why are we solving this issue? > - To address this issue, are there...

In #1685 I previously suggested _plan simulations_: https://github.com/opentofu/opentofu/issues/1685#issuecomment-2154252778 However, I now think it'd be handy to provide a way to say "here is a file [that some tool has written]...

There is a KEP for [dynamic resource allocation](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3063-dynamic-resource-allocation). That architecture allows a Pod to find a node where some suitable GPU exists, even where the node has multiple GPUs. Those...

This needs a real release note; it's not mergeable as is @tkashem.

@tallclair we should have some changes to https://kubernetes.io/docs/concepts/workloads/pods/ too - especially if there's a plan to move this to enabled-by-default and / or to beta.

> Feature naming consistency, centered around "Resizing CPU and Memory Resources in-place" We document _concepts_ and _tasks_ much more than features. We should write the docs mostly as if Kubernetes...