example/connectivity-check: fix port conflict, capture termination log #28833
Conversation
This file contains 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
squeed
added
area/CI
It was discovered that these containers listen in the NodePort range by default, opening them up to random flakes if there's a NodePort service that happens to be there. So, move the listening port out of that range. Also, add a reasonable TerminationMessagePolicy so we can capture error status on exit. Fixes: cilium#28832 Signed-off-by: Casey Callendrello <cdc@isovalent.com>
squeed
force-pushed
the
test-fix-port-collision
branch
from
9e60a1c
to
4fb5800
Compare
|
/test |
maintainer-s-little-helper
bot
added
the
ready-to-merge
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.
It was discovered that these containers listen in the NodePort range by default, opening them up to random flakes if there's a NodePort service that happens to be there.
So, move the listening port out of that range.
Also, add a reasonable TerminationMessagePolicy so we can capture error status on exit.
Fixes: #28832