-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[ws-manager] config terminationGracePeriodSeconds #13352
Conversation
started the job as gitpod-build-se-flexible-termination-period.1 because the annotations in the pull request description changed |
4d83eb9
to
65b686f
Compare
/werft run 👍 started the job as gitpod-build-se-flexible-termination-period.3 |
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.
What's the general release plan for this feature? Are we looking to control access to the termination grace period somehow?
/hold for Qs
@@ -114,6 +114,10 @@ | |||
"additionalProperties": false | |||
} | |||
}, | |||
"terminationGracePeriodSeconds": { |
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.
In the protocol it's marked as optional, does it need to be marked optional here too?
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.
By making this change, all requests will now be able to set this despite it not being actually implemented by workspaces. Is that intended? Do we want to control release of this in some way?
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.
In the protocol it's marked as optional, does it need to be marked optional here too?
it is optional by default
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.
Ah, it used to have optional
in the v2 version of the spec. in v4
it only has required
. Thanks!
@@ -567,6 +567,9 @@ message StartWorkspaceSpec { | |||
|
|||
// ssh_public_keys is user's uploaded ssh public keys | |||
repeated string ssh_public_keys = 15; | |||
|
|||
// termination_grace_period_seconds sets the TerminationGracePeriodSeconds, defaults to 30 seconds | |||
int64 termination_grace_period_seconds = 16; |
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.
Worth keeping in mind that ws-manager
running in WS clusters will have a different rollout cadence to webapp. This change is backwards compatible so it shouldn't be a system problem, just an expectation.
btw. the bash process we are starting doesn't seem to propagate SIGINT to the process it is waiting for. |
We have quite a few places where we pass in a termination grace period, e.g. all call sites of |
@csweichel |
65b686f
to
616fb25
Compare
55caad1
to
0e9d536
Compare
Which indeed means that the value we use for We could either (in descending order of implementation complexity)
|
I've set it to the same hard-coded max (5 minutes). (see) |
377dfde
to
222dbfb
Compare
started the job as gitpod-build-se-flexible-termination-period.9 because the annotations in the pull request description changed |
/hold |
e5b13f1
to
5939f9c
Compare
5939f9c
to
36923c6
Compare
/werft run with-clean-slate-deployment 👍 started the job as gitpod-build-se-flexible-termination-period.14 |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Description
Allow extending the termination grace period of workspace pods through gitpod.yml configuration.
Related Issue(s)
Fixes #
How to test
ignoreSigterm > out.txt
out.txt
should contain log messages that show the process ran almost 100 seconds after receiving the SIGHUPRelease Notes
Documentation
Werft options:
If enabled this will build
install/preview
Valid options are
all
,workspace
,webapp
,ide