The Kubernetes project has announced that the in-place Pod resize feature has graduated to Beta and will be enabled by default in the Kubernetes v1.33 release. This feature allows users to change the CPU and memory resources allocated to a container without requiring a container restart. In-place Pod resizing unlocks several key benefits for vertical scaling, including reduced disruption, improved resource utilization, and faster scaling. The feature has undergone significant changes since its alpha release, including the introduction of a resize subresource, resize status via conditions, and sidecar support. The stability and reliability of the feature have been enhanced through refined allocated resources management, improved checkpointing and state tracking, and faster resize detection. The community is focusing on next steps, including stability and productionization, addressing limitations, and integrating with VerticalPodAutoscaler. Users can start experimenting with in-place Pod resizing with the feature gate enabled by default. Feedback is crucial, and users can report any problems or share their experiences through GitHub issues, mailing lists, and Slack. The full in-depth design details can be found in the KEP-1287: In-place Update of Pod Resources. The Kubernetes community looks forward to seeing how users leverage in-place Pod resize to build more efficient and resilient applications.