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.
following your request in the PR #1603, i am recreating this in order to push it in the dev branch.
besides the description in the old PR, here is an example of how this will reduce amount of logs in the bunkerweb controller pod.
here is the logs before adding my commit:
as you may notice, the name of the service is not known, as well as the amount of logs that's keeps showing in the pod's logs.
After adding my commit, you'll have something like this:
in my case, it was my ingress hubble configured this way:
for all deployed ingresses that will be based on port name instead of port numbers, you'll only have one unique log entry for each ingress along with the ingress name.