Cherry-pick #19052 to 7.x: Fix incorrect usage of hints builder when exposed port is a substring of the hint #19163
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.
Cherry-pick of PR #19052 to 7.x branch. Original message:
Type of change - Bug
What does this PR do?
This PR makes sure that if a user exposes port
80and has8080on the metric hint, then we dont use that port to do the autodiscover as the port could be exposed on another containerWhy is it important?
This is important as this impacts what container metadata gets appended to the metric.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
How to test this PR locally
Related issues
Use cases