We need to eventually remove the opt-in for the behavior where Kubelet fails with swap enabled. Swap enabled should be an error by default.
This can't be done immediately because we need to maintain legacy behavior.
TODO introduced in: https://github.com/kubernetes/kubernetes/issues/34463
Please reconsider this option, we leverage the zram module to enable volatile swap space for our custom RHEL-based distribution using a systemd service file zramswap.service
1:
16:15:41 csos-builder ~ # systemctl cat zramswap.service
# /usr/lib/systemd/system/zramswap.service
[Unit]
Description=Zram-based swap (compressed RAM block devices)
[Service]
Type=oneshot
ExecStart=/usr/lib/systemd/scripts/zramctrl start
ExecStop=/usr/lib/systemd/scripts/zramctrl stop
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target
Could anyone be able to explain the technical merits behind making this decision in the first place?
Thanks in advance.
Most helpful comment
Please reconsider this option, we leverage the zram module to enable volatile swap space for our custom RHEL-based distribution using a systemd service file
zramswap.service
1:Could anyone be able to explain the technical merits behind making this decision in the first place?
Thanks in advance.
1: https://aur.archlinux.org/packages/zramswap/