Kubernetes v1.33 introduces updates to the lifecycle of containers, including support for a zero sleep duration in container lifecycle hooks. The Sleep action, introduced in v1.29, allows containers to pause for a specified time after starting or before termination. Initially, the Sleep action did not support a zero sleep duration, but this was added in v1.32 and is now enabled by default in v1.33. Kubernetes v1.33 also introduces alpha support for customizing the stop signal sent to containers when they are being terminated. This allows users to specify a custom stop signal in the container spec, which is added to the API as a new lifecycle handler. The stop signal configuration is enforced to ensure it is valid for the node the Pod is scheduled on. If no custom stop signal is defined, the container runtime will fallback to the stop signal defined in the container image or the default signal of the runtime. The feature requires both the Kubernetes and container runtime to support container stop signals, which is still a work in progress. To enable the feature, users must turn on the feature gate in both the kube-apiserver and the kubelet. The SIG Node team is driving this feature and welcomes feedback, participation, and involvement from the community.