-
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] Watch VolumeSnapshot object and notify to the Pod finalizer loop #10820
Conversation
Add volume_snapshot_controller to watch the VolumeSnapshot object. Signed-off-by: JenTing Hsiao <hsiaoairplane@gmail.com>
started the job as gitpod-build-jenting-ws-manager-volume-snapshot-10334.7 because the annotations in the pull request description changed |
90f7034
to
038827c
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.
can you also give my user admin access in preview env so that I can test this PR? Thank you!
When the VolumeSnapshot object is ready, notify to the Pod that it belongs to. Signed-off-by: JenTing Hsiao <hsiaoairplane@gmail.com>
038827c
to
38f3cf7
Compare
Added, PTAL 🙏 |
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.
code looks good.
adding hold to do a test in preview env (waiting for an admin role from @jenting )
/hold
/unhold tested, works like a charm! |
Description
Add volume_snapshot_controller to watch the VolumeSnapshot object, and once the VolumeSnapshot object is ready, notify the Pod in the finalizer loop that the VolumeSnapshot is ready.
This improves the volume snapshot metric
gitpod_ws_manager_volume_snapshot_seconds
more accurately when the workspace stops.Related Issue(s)
Fixes #10334
How to test
kubectl get vs -w
kubectl port-forward <ws-manager-pod> 9500:9500
curl -XGET 'localhost:9500/metrics' | grep gitpod_ws_manager_volume_snapshot_seconds
, and check if the time matches step 2.Release Notes
Documentation
None
Werft options: