-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for containerd to antrea-eks-node-init.yml #3840
Add support for containerd to antrea-eks-node-init.yml #3840
Conversation
I'm going to run the cloud CI on my branch for testing |
Codecov Report
@@ Coverage Diff @@
## main #3840 +/- ##
=======================================
Coverage 47.70% 47.70%
=======================================
Files 256 256
Lines 37092 37092
=======================================
Hits 17693 17693
Misses 17673 17673
Partials 1726 1726
Flags with carried forward coverage won't be shown. Click here to find out more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nits.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, a type in commit message: ensuire
/skip-all |
ebc43e4
to
d8f3572
Compare
Containerd is available as an alternative to docker since EKS v1.21. Starting with EKS v1.23, containerd will also be the default container runtime. Currently antrea-eks-node-init.yml assumes that docker is always the container runtime, which means that Antrea cannot be run on EKS clusters using containerd. We fix this by adding support for containerd. We also make a couple of improvements to the startup script in antrea-eks-node-init.yml, to ensure that it can be run again if the contents of the script change, which is useful for testing and may also be useful to roll out patches. Finally, we update our EKS CI to test with containerd instead of docker, since containerd will be the default soon. Fixes antrea-io#3471 Signed-off-by: Antonin Bas <abas@vmware.com>
d8f3572
to
f82f51e
Compare
/skip-all |
Containerd is available as an alternative to docker since EKS
v1.21. Starting with EKS v1.23, containerd will also be the default
container runtime. Currently antrea-eks-node-init.yml assumes that
docker is always the container runtime, which means that Antrea cannot
be run on EKS clusters using containerd. We fix this by adding support
for containerd.
We also make a couple of improvements to the startup script in
antrea-eks-node-init.yml, to ensure that it can be run again if the
contents of the script change, which is useful for testing and may
also be useful to roll out patches.
Finally, we update our EKS CI to test with containerd instead of docker,
since containerd will be the default soon.
Fixes #3471
Signed-off-by: Antonin Bas abas@vmware.com