Skip to content
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

Merged

Conversation

haircommander
Copy link
Member

- 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

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>
@mrunalp
Copy link
Member

mrunalp commented Oct 23, 2020

We should do a few runs before merging this.

Copy link
Member

@cgwalters cgwalters left a 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?

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 23, 2020
@openshift-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 23, 2020
@mrunalp
Copy link
Member

mrunalp commented Oct 23, 2020

/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 23, 2020
@mrunalp
Copy link
Member

mrunalp commented Oct 23, 2020

@cgwalters The regular e2e test runs should catch regressions, if any.

@mrunalp
Copy link
Member

mrunalp commented Oct 23, 2020

/retest

@rphillips
Copy link
Contributor

rphillips commented Oct 23, 2020

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.

@haircommander
Copy link
Member Author

/retest

@haircommander
Copy link
Member Author

/test all

@haircommander
Copy link
Member Author

hm doesn't look related
/test all

@haircommander
Copy link
Member Author

/retest

@haircommander
Copy link
Member Author

/test all

@haircommander
Copy link
Member Author

/retest

2 similar comments
@haircommander
Copy link
Member Author

/retest

@haircommander
Copy link
Member Author

/retest

@mrunalp
Copy link
Member

mrunalp commented Nov 2, 2020

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 2, 2020
@cgwalters
Copy link
Member

/override ci/prow/okd-e2e-upgrade
/override ci/prow/okd-e2e-gcp-op

@openshift-ci-robot
Copy link
Contributor

@cgwalters: /override requires a failed status context to operate on.
The following unknown contexts were given:

  • ci/prow/okd-e2e-gcp-op
  • ci/prow/okd-e2e-upgrade

Only the following contexts were expected:

  • ci/prow/e2e-agnostic-upgrade
  • ci/prow/e2e-aws
  • ci/prow/e2e-aws-workers-rhel7
  • ci/prow/e2e-gcp-op
  • ci/prow/e2e-metal-ipi
  • ci/prow/e2e-ovn-step-registry
  • ci/prow/images
  • ci/prow/okd-e2e-aws
  • ci/prow/okd-images
  • ci/prow/unit
  • ci/prow/verify
  • tide

In response to this:

/override ci/prow/okd-e2e-upgrade
/override ci/prow/okd-e2e-gcp-op

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.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

3 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

2 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants