-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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] Introduce stoppedByRequest condition #6218
Conversation
Codecov Report
@@ Coverage Diff @@
## main #6218 +/- ##
==========================================
+ Coverage 33.96% 39.37% +5.40%
==========================================
Files 130 13 -117
Lines 22323 3779 -18544
==========================================
- Hits 7583 1488 -6095
+ Misses 14059 2168 -11891
+ Partials 681 123 -558
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
/lgtm |
LGTM label has been added. Git tree hash: be58609f12e98e4acfd706514fd430a372a1d15e
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aledbf Associated issue: #6213 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 |
Description
This PR changes the stopping behaviour of ws-manager so that when
StopWorkspace
is called we first mark the workspace with agitpod.io/stoppedByRequest
annotation which contains the desired termination grace period. This annotation also backs a newstoppedByRequest
annotation on the workspace status. This condition can be used to determine if the workspace was stopped by explicit request, e.g. to signal prebuild cancelation.Related Issue(s)
Fixes #6213
How to test
gpctl workspaces subscribe --output-template '{{ .Id }} {{ .Phase }} {{ .Conditions }}'
stoppedByRequest
annotation is setRelease Notes