Skip to content

Conversation

@saschagrunert
Copy link
Member

What type of PR is this?

/kind feature

What this PR does / why we need it:

We can use the deadline from the CRI context for stopping containers. This allows a more dynamic behavior compared to the static 10s before. Tools like crictl can be used to remove containers given a strict timeout this way.

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

None

Does this PR introduce a user-facing change?

Use the context timeout / deadline for stopping containers if provided.

@openshift-ci openshift-ci bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. kind/feature Categorizes issue or PR as related to a new feature. labels Oct 15, 2024
@openshift-ci openshift-ci bot requested review from klihub and littlejawa October 15, 2024 09:29
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 15, 2024
@saschagrunert saschagrunert force-pushed the container-stop-timeout branch 2 times, most recently from b78b2d2 to 16f13b3 Compare October 15, 2024 09:36
@kwilczynski
Copy link
Contributor

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 15, 2024
@saschagrunert saschagrunert force-pushed the container-stop-timeout branch from 16f13b3 to a20dbca Compare October 15, 2024 09:42
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 15, 2024
@kwilczynski
Copy link
Contributor

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 15, 2024
@codecov
Copy link

codecov bot commented Oct 15, 2024

Codecov Report

Attention: Patch coverage is 0% with 9 lines in your changes missing coverage. Please review.

Project coverage is 48.79%. Comparing base (f8f4414) to head (2a42045).
Report is 6 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #8678      +/-   ##
==========================================
- Coverage   48.86%   48.79%   -0.07%     
==========================================
  Files         153      153              
  Lines       17376    17388      +12     
==========================================
- Hits         8491     8485       -6     
- Misses       7822     7843      +21     
+ Partials     1063     1060       -3     

@saschagrunert
Copy link
Member Author

/test ci-fedora-kata

@saschagrunert saschagrunert force-pushed the container-stop-timeout branch from a20dbca to 630877f Compare October 15, 2024 11:18
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 15, 2024
@saschagrunert saschagrunert force-pushed the container-stop-timeout branch from 630877f to c45f507 Compare October 15, 2024 12:21
@kwilczynski
Copy link
Contributor

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 15, 2024
@saschagrunert saschagrunert force-pushed the container-stop-timeout branch from c45f507 to ee80232 Compare October 15, 2024 13:02
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 15, 2024
We can use the deadline from the CRI context for stopping containers.
This allows a more dynamic behavior compared to the static 10s before.
Tools like `crictl` can be used to remove containers given a strict
timeout this way.

Signed-off-by: Sascha Grunert <[email protected]>
@saschagrunert saschagrunert force-pushed the container-stop-timeout branch from ee80232 to 2a42045 Compare October 15, 2024 13:04
@saschagrunert
Copy link
Member Author

/retest

1 similar comment
@saschagrunert
Copy link
Member Author

/retest

@saschagrunert
Copy link
Member Author

/retest

@saschagrunert
Copy link
Member Author

@cri-o/cri-o-maintainers PTAL again

@saschagrunert
Copy link
Member Author

/retest

2 similar comments
@saschagrunert
Copy link
Member Author

/retest

@saschagrunert
Copy link
Member Author

/retest

@saschagrunert
Copy link
Member Author

@cri-o/cri-o-maintainers PTAL

@kwilczynski
Copy link
Contributor

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 16, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 16, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kwilczynski, saschagrunert

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-merge-bot openshift-merge-bot bot merged commit 7049bb9 into cri-o:main Oct 16, 2024
79 of 82 checks passed
@saschagrunert saschagrunert deleted the container-stop-timeout branch October 16, 2024 12:13
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. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants