A naukri.com initiative
Kubernetes
3w
373
Kubernetes v1.33: Updates to Container Lifecycle
- Kubernetes v1.33 introduces updates to the container lifecycle with features like zero value for Sleep action and customizing stop signals.
- The Sleep action now supports a zero sleep duration, allowing containers to pause before termination.
- Customizing stop signals is in alpha stage, enabling users to specify a custom stop signal for container termination.
- The PodLifecycleSleepActionAllowZero feature gate in v1.33 enables zero duration for sleep hooks by default.
- Container runtimes honor StopSignal instruction to terminate containers with custom signals.
- Pods in Kubernetes v1.33 can specify a custom stop signal using the newly added ContainerStopSignals feature gate.
- Containers without custom stop signals fall back to the default stop signal of the runtime, which is SIGTERM for containerd and CRI-O.
- Both Kubernetes version and container runtime need to support stop signals for this feature to work correctly.
- To use custom stop signals, ContainerStopSignals feature gate needs to be enabled in kube-apiserver and kubelet.
- Users can configure container stop signals based on the OS, differentiating between Linux and Windows nodes.
- For those interested in contributing or providing feedback on this feature, reaching out to SIG Node is recommended.
Read Full Article
22 Likes
For uninterrupted reading, download the app