Skip to content

[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

Merged
merged 1 commit into from
Jan 27, 2023
Merged

Conversation

WVerlaek
Copy link
Member

@WVerlaek WVerlaek commented Jan 26, 2023

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

NONE

Documentation

Build Options:

  • /werft with-github-actions
    Experimental feature to run the build with GitHub Actions (and not in Werft).
  • leeway-no-cache
    leeway-target=components:all-ci
  • /werft no-test
    Run Leeway with --dont-test

Preview Environment Options:

  • /werft with-local-preview
    If enabled this will build install/preview
  • /werft with-preview
  • /werft with-large-vm
  • /werft with-gce-vm
    If enabled this will create the environment on GCE infra
  • /werft with-integration-tests=all
    Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh

@werft-gitpod-dev-com
Copy link

started the job as gitpod-build-wv-ws-manager-mk2-todos.4 because the annotations in the pull request description changed
(with .werft/ from main)

@WVerlaek WVerlaek force-pushed the wv/ws-manager-mk2-todos branch 3 times, most recently from 9553671 to e5cce2c Compare January 26, 2023 10:02
@WVerlaek WVerlaek force-pushed the wv/ws-manager-mk2-todos branch from e5cce2c to b1ed4b4 Compare January 26, 2023 10:09
@WVerlaek WVerlaek changed the title [ws-manager-mk2] Configure health probes and leader election [ws-manager-mk2] Configure health probes Jan 26, 2023
@werft-gitpod-dev-com
Copy link

started the job as gitpod-build-wv-ws-manager-mk2-todos.10 because the annotations in the pull request description changed
(with .werft/ from main)

@werft-gitpod-dev-com
Copy link

started the job as gitpod-build-wv-ws-manager-mk2-todos.11 because the annotations in the pull request description changed
(with .werft/ from main)

@WVerlaek WVerlaek marked this pull request as ready for review January 26, 2023 10:12
@WVerlaek WVerlaek requested a review from a team January 26, 2023 10:12
@WVerlaek WVerlaek self-assigned this Jan 26, 2023
@github-actions github-actions bot added the team: workspace Issue belongs to the Workspace team label Jan 26, 2023
@werft-gitpod-dev-com
Copy link

started the job as gitpod-build-wv-ws-manager-mk2-todos.12 because the annotations in the pull request description changed
(with .werft/ from main)

@WVerlaek
Copy link
Member Author

WVerlaek commented Jan 26, 2023

/werft run -a recreate-vm=true

👍 started the job as gitpod-build-wv-ws-manager-mk2-todos.13
(with .werft/ from main)

@roboquat roboquat merged commit 3651262 into main Jan 27, 2023
@roboquat roboquat deleted the wv/ws-manager-mk2-todos branch January 27, 2023 03:12
@roboquat roboquat added deployed: workspace Workspace team change is running in production deployed Change is completely running in production labels Jan 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deployed: workspace Workspace team change is running in production deployed Change is completely running in production release-note-none size/M team: workspace Issue belongs to the Workspace team
Projects
No open projects
Status: Done
Development

Successfully merging this pull request may close these issues.

4 participants