-
Notifications
You must be signed in to change notification settings - Fork 129
UPSTREAM: <carry>: kube-apiserver: ignore SIGTERM/INT after the first one #616
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
Conversation
|
@damemi: the contents of this pull request could not be automatically validated. The following commits could not be validated and must be approved by a top-level approver:
|
damemi
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.
/cc @sttts
do we need a bz for this?
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.
all the cases with true you can revert to be just server.SetupSignalHandler().
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.
would avoid copying code. You can do:
func SetupSignalContextNotExiting() context.Context {
return setupSignalContext(false)
}
func SetupSignalContext() context.Context {
return setupSignalContext(true)
}
func setupSignalContext(exitOnSecondSignal bool) context.Context {
...
}
|
@damemi: the contents of this pull request could not be automatically validated. The following commits could not be validated and must be approved by a top-level approver:
|
…ctions to ignore further signals This patches the changes from openshift#558 to provide these new functions without changing the behavior for other repos that depend on them, such as library-go.
|
@sttts ping, squashed the commits here. Could you ptal? |
|
@damemi: the contents of this pull request could not be automatically validated. The following commits could not be validated and must be approved by a top-level approver:
|
|
/retest |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: damemi, sttts 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 |
|
Looks like this still has |
|
It needs to be approved by a top-level approver I think? Maybe @smarterclayton could take a look? |
That's a novel thing - updated, should merge shortly. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/test k8s-e2e-gcp |
|
/cherry-pick release-4.7 |
|
@damemi: new pull request created: #739 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/test-infra repository. |
This partially reverts some of the changes from #558 to provide the new functions for areas that need them, while keeping the old functions so as to not affect other repos that depend on them (like library-go, see openshift/library-go#1008)