I see that containerd already supports handling swap limits passed on via CRI. With NodeSwap feature gate enabled everything works great since kubelet takes care of passing the MemorySwapLimitInBytes. But if this feature isn't enabled we end up setting swap limit to zero which can result in container using swap given if memory limit was specified. Is that the expected behavior? I see cri-dockerd/dockershim is setting both swap/memory limit to same value to avoid this?

// Memory and MemorySwap are set to the same value, this prevents containers from using any swap.
Memory:     rOpts.MemoryLimitInBytes,
MemorySwap: rOpts.MemoryLimitInBytes,

I believe the default should be to disable the swap for containers by setting same memory/swap limits given CRI doesn't provide any value. My concern is if a user migrates from dockershim to containerd they should have a consistent experience? Would love to hear your feedback and happy to propose a PR if needed.