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
crio: drop infra container when possible #2177
crio: drop infra container when possible #2177
Conversation
in cri-o 1.19 we introduced a feature to drop the infra container when a pod doesn't have a pod level PID namespace We have been running with this option in cri-o internal tests and have seen no issues. Let's enable it by default in 4.7. In addition to being more performant, it also should aid in a race with the kubelet win-win! Signed-off-by: Peter Hunt <pehunt@redhat.com>
We should do a few runs before merging this. |
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
Is there an e2e covering this?
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cgwalters, haircommander The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold |
@cgwalters The regular e2e test runs should catch regressions, if any. |
/retest |
We want to let this bake for a few runs in CI before merging, thus the hold. The e2e-agnostic-upgrade failed on a GCE error. |
/retest |
/test all |
hm doesn't look related |
/retest |
/test all |
/retest |
2 similar comments
/retest |
/retest |
/hold cancel |
/override ci/prow/okd-e2e-upgrade |
@cgwalters: /override requires a failed status context to operate on.
Only the following contexts were expected:
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/retest Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
- What I did
in cri-o 1.19 we introduced a feature to drop the infra container when a pod doesn't have a pod level PID namespace
We have been running with this option in cri-o internal tests and have seen no issues.
Let's enable it by default in 4.7. In addition to being more performant, it also should aid in a race with the kubelet
win-win!
Signed-off-by: Peter Hunt pehunt@redhat.com
- How to verify it
- Description for the changelog
Have CRI-O drop the infra container in some cases, which performs better