-
Notifications
You must be signed in to change notification settings - Fork 1.6k
KEP-3998: Update the metrics and condition reason for the Beta graduation #4775
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
KEP-3998: Update the metrics and condition reason for the Beta graduation #4775
Conversation
|
I updated the JobSuccessPolicy Beta graduation KEP based on discussions during the implementation phase. /assign @atiratree @mimowo @alculquicondor @soltysh |
|
/lgtm |
|
@soltysh Could you take a look at this? Thanks! |
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 cancel
minor nits, and this is good to land, please ping me on slack when you get this updated :-)
|
|
||
| # The following PRR answers are required at beta release | ||
| metrics: | ||
| - job_succeeded_total |
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.
This should state jobs_finished_total based on the update, not a removal of a metric, which is one of the requirement for almost every enhancement.
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.
It doesn't mean it has to be new metrics, but ones that are relevant for observing the state of the cluster after the feature is being used. With that I'd also add job_sync_duration_seconds which you mentioned in the SLI section of the enhancement.
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.
I did not know that. Thank you for the kindly guidance.
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.
done.
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.
+1, I think jobs_finished_total should still be added to the list per first 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.
Good point. Thanks.
I added that.
f537c36 to
e060145
Compare
Signed-off-by: Yuki Iwai <[email protected]>
e060145 to
893cd43
Compare
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
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
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: soltysh, tenzen-y 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 |
jobs_finished_totalmetric reasons and theCompleteandSuccessCriteriaMetcondition reasons.