-
Notifications
You must be signed in to change notification settings - Fork 71
✨ Support ClusterExtension progress deadline detection
#2447
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
✨ Support ClusterExtension progress deadline detection
#2447
Conversation
✅ Deploy Preview for olmv1 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
4dbbdd5 to
98f42da
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2447 +/- ##
==========================================
- Coverage 69.48% 69.43% -0.06%
==========================================
Files 101 101
Lines 7701 7730 +29
==========================================
+ Hits 5351 5367 +16
- Misses 1914 1927 +13
Partials 436 436
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
98f42da to
5ed4b38
Compare
ClusterExtension progress deadline detection
4eaad24 to
9788589
Compare
internal/operator-controller/controllers/clusterextensionrevision_controller.go
Show resolved
Hide resolved
internal/operator-controller/controllers/clusterextensionrevision_controller.go
Show resolved
Hide resolved
internal/operator-controller/controllers/clusterextensionrevision_controller.go
Show resolved
Hide resolved
9788589 to
c0a66ab
Compare
Adds optional `.spec.progressDeadlineMinutes` field to `ClusterExtension` and `ClusterExtensionRevision` that defines the maximum time an extension version can take to roll out before being marked as failed. When configured, if a `ClusterExtensionRevision` fails to roll out within the specified duration, the `Progressing` condition is set to `False` with reason `ProgressDeadlineExceeded`. This signals that manual intervention is required and stops automatic retry attempts. Added unit and e2e test asserting the added behavior.
c0a66ab to
a830bc8
Compare
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: perdasilva 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 |
camilamacedo86
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
|
/override codecov/patch |
|
@pedjak: Overrode contexts on behalf of pedjak: codecov/patch DetailsIn 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-sigs/prow repository. |
a9e5614
into
operator-framework:main
Description
Adds optional
.spec.progressDeadlineMinutesfield toClusterExtensionand
ClusterExtensionRevisionthat definesthe maximum time an extension version can take to roll out before being marked as failed.
When configured, if a
ClusterExtensionRevisionfails to roll out withinthe specified duration, the
Progressingcondition is set toFalsewith reasonProgressDeadlineExceeded. This signals that manual intervention is requiredand stops automatic retry attempts.
Added unit and e2e test asserting the added behavior.
Reviewer Checklist