-
Notifications
You must be signed in to change notification settings - Fork 53
Add containerd 2.0 #485
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 containerd 2.0 #485
Conversation
packages/containerd-2.0/1002-Upgrade-systemd-config-for-packaging.patch
Outdated
Show resolved
Hide resolved
packages/containerd-2.0/1002-Upgrade-systemd-config-for-packaging.patch
Outdated
Show resolved
Hide resolved
packages/containerd-2.0/1002-Upgrade-systemd-config-for-packaging.patch
Outdated
Show resolved
Hide resolved
packages/containerd-2.0/1002-Upgrade-systemd-config-for-packaging.patch
Outdated
Show resolved
Hide resolved
76dbdc6 to
be95490
Compare
|
^ Pushed suggested changes - still open to do further pause image verification. |
bcressey
left a comment
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.
It's hard to comment on containerd-1.7.spec, but most of these fixes are needed there also.
Signed-off-by: Kyle Sessions <kssessio@amazon.com>
Signed-off-by: Kyle Sessions <kssessio@amazon.com>
|
^ force push the suggested updates, and added additional Additionally replied back on the pause container threads. |
| LimitCORE=infinity | ||
| LimitNOFILE=infinity | ||
| TasksMax=infinity | ||
| OOMScoreAdjust=-999 |
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.
nit: this would be good to apply to containerd 1.7 also
Since we've been burned by similar changes in the past, where service changes "leak" across to containers, it would be good to double check that OOM scores for pod cgroups aren't affected.
The output of this should not look very different before and after:
head /proc/*/oom_score_adj
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.
Before launched a simple pod with containerd 1.7:
sh-5.2# head /proc/*/oom_score_adj
==> /proc/1/oom_score_adj <==
981
==> /proc/23/oom_score_adj <==
981
==> /proc/24/oom_score_adj <==
1000
==> /proc/25/oom_score_adj <==
981
==> /proc/self/oom_score_adj <==
981
==> /proc/thread-self/oom_score_adj <==
981
After same pod on containerd 1.7 w/ OOMScoreAdjust=-999
sh-5.2# head /proc/*/oom_score_adj
==> /proc/1/oom_score_adj <==
981
==> /proc/23/oom_score_adj <==
981
==> /proc/24/oom_score_adj <==
1000
==> /proc/25/oom_score_adj <==
981
==> /proc/self/oom_score_adj <==
981
==> /proc/thread-self/oom_score_adj <==
981
| "packages/conntrack-tools", | ||
| "packages/containerd", | ||
| "packages/containerd-1.7", | ||
| "packages/containerd-2.0", |
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.
Is the plan to add another package for containerd-2.1, and all the subsequent 2.x minor versions too?
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.
If we have multiple versions of containerd in the core kit, yes they will be versioned out.
I think i'd like us to work towards getting back to 1 containerd package....eventually.
Signed-off-by: Kyle Sessions <kssessio@amazon.com>
|
^ Added OOMScoreAdjust to containerd 1.7 and fixed the spec comment. |
Signed-off-by: Kyle Sessions <kssessio@amazon.com>
|
^ Added a missing comment - and formed an overall diff gist. |
henry118
left a comment
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
Issue number:
Closes #256
Description of changes:
Add containerd 2.0 as a package
Major Diffs:
Testing done:
ContainerD 2.0 Testing
0. Version running:
Also from a cluster:
1. Conformance test results on different Kernels:
2. Load test
Ran internal load test on 1.32 k8s AMI for 72Hr (so far - will update). Did not see any issue.
All metrics were stable during the testing:
3. NRI
Tested NRI Plugin: https://containers.github.io/nri-plugins/stable/docs/resource-policy/policy/topology-aware.html
Deployed 3 containers with separate resource requests.
Before NRI on
x1e.32xlargeinspected:/proc/self/statusin the containers:After NRI on
x1e.32xlargeinspected:/proc/self/statusin the containers:On
m5.largeandg5.largeno change from before and after the topology.On
m6g.xlargeverified a simple self created hello world NRI plugin.Recursive Read-only (RRO) mounts:
Verified new RRO feature:
Variant Build test:
containerd-2.0on x86containerd-2.0(optimized-gunzip)on aarch64containerd-2.0(optimized-gunzip)on x86containerd-pigzcontainerd-2.0andcontainerd-pigzTerms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.