Run cleanup job on each Werft build node #9905
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/werft run 👍 started the job as gitpod-build-mads-cleanup-all-nodes.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
/werft no-preview
Description
This ensure we run the cleanup logic on each build node by splitting the job into two, one to perform the cleanup logic, and one to trigger it for each node.
platform-clean-up-werft-build-nodes.yamltoplatform-clean-up-werft-build-node.yaml(singular) and changed the job spec so that the nodeAffinity is based on a job annotation..werft/platform-trigger-werft-cleanup.yamlwhich lists all nodes withdev/workloadlabel set tobuildsand triggers theplatform-clean-up-werft-build-node.yamljob for that node.In a follow up PR we'll change the
platform-clean-up-werft-build-node.yamlto cordon the node if it is running too low on disk.Related Issue(s)
Part of https://github.com/gitpod-io/ops/issues/2050
How to test
As described in the comments in the Werft job specs.
Release Notes
Documentation
N/A