Improve werft job build speed and make honeycomb more accurate #8577
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.
Description
Current werft job honeycomb shows that
pull image secret
take a long time, which is not accurate, because we don't DONEpull image secret
slice for some conditionsAnd
reuse last port
almost not work, this takes really long time to get used port, because we always want to getnode-exporter
port, which is only enable bywithObservability
flag.This PR fixes these
Related Issue(s)
Fixes #
How to test
Comment
/werft run
in this PR to see werft job log and honeycombRelease Notes
Documentation