Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Description of changes:
Not totally sure why but using cgroupns=private on AL2 nodes, this did not seem to be an issue on Ubuntu 20.04 nodes which is also cgroup v1, seems to cause issues creating the containers instead the kind node image.
Kind 0.20 does call out that using cgroupns=default with cgroupv1 is deprecated and will eventually be removed. The code to handle this case has been in the entrypoint.sh script for quite some time and we can continue to maintain this in our patches if necessary.
Newer distro, Ubuntu 22.04 and AL23, use cgroup v2 which are not affected by this change since docker already defaults to cgroupns=private for cgroup v2 hosts.
I confirmed this issue exist on an AL2 using the upstream kind binary and upstream kind node image as well. Using this patched version of kind, I was able to create a cluster with both the upstream image and the eks-a al23 based node image.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.