Bump operator-lib to v0.13.0#483
Conversation
|
@ravitri: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #483 +/- ##
=======================================
Coverage 54.22% 54.22%
=======================================
Files 122 122
Lines 5953 5953
=======================================
Hits 3228 3228
Misses 2523 2523
Partials 202 202 |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ravitri, Tafhim The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
(dependency update)
What this PR does / why we need it?
This PR updates the
github.com/operator-framework/operator-libversion to v0.13.0. The main reason to do that was to avail the fix for upstream issue operator-framework/operator-lib#156 identified in version v0.12.0.With the fix in operator-framework/operator-lib#157, we will additionally address the issue scenario of MUO lock not released incase the pod is preempted. If we continue to face the issue ahead as well after rollout of this PR, we can review and consider PR #476 solution further ahead.
Which Jira/Github issue(s) this PR fixes?
Fixes # OSD-25179
Special notes for your reviewer:
This PR would atleast partially address the concern that PR #476 intended to address with a dependency bump so would be ok to close the other PR for time being and get back to it if we still continue to face similar issue.
Pre-checks (if applicable):