-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[ws-manager-mk2] Configure health probes #16041
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
started the job as gitpod-build-wv-ws-manager-mk2-todos.4 because the annotations in the pull request description changed |
9553671
to
e5cce2c
Compare
e5cce2c
to
b1ed4b4
Compare
started the job as gitpod-build-wv-ws-manager-mk2-todos.10 because the annotations in the pull request description changed |
started the job as gitpod-build-wv-ws-manager-mk2-todos.11 because the annotations in the pull request description changed |
started the job as gitpod-build-wv-ws-manager-mk2-todos.12 because the annotations in the pull request description changed |
/werft run -a recreate-vm=true 👍 started the job as gitpod-build-wv-ws-manager-mk2-todos.13 |
Description
Configure readiness and liveness probes for ws-manager-mk2, using the controller manager's health probe endpoints.
Related Issue(s)
Relates to #11416
How to test
Open preview env, check health probes are working on the ws-manager-mk2 deployment
Release Notes
Documentation
Build Options:
Experimental feature to run the build with GitHub Actions (and not in Werft).
leeway-target=components:all-ci
Run Leeway with
--dont-test
Preview Environment Options:
If enabled this will build
install/preview
If enabled this will create the environment on GCE infra
Valid options are
all
,workspace
,webapp
,ide
,jetbrains
,vscode
,ssh