fix: use fully-qualified DNS name in Fluent Bit ClusterOutput #1796
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
Update the Fluent Bit forward ClusterOutput template to use the fully-qualified domain name (.svc.cluster.local) instead of the partially qualified name (.svc) to ensure reliable service discovery across all namespaces and prevent cross-namespace DNS resolution issues. Fixes fluent#1794 Signed-off-by: snoop123 <snooppit@gmail.com> Signed-off-by: snoop123 <30404303+snoop123@users.noreply.github.com>
marcofranssen
force-pushed
the
patch-1
branch
from
f5a60fa to
83195c7
Compare
marcofranssen
approved these changes
Nov 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Update the Fluent Bit forward ClusterOutput template to use the fully-qualified domain name (.svc.cluster.local) instead of the partially qualified name (.svc) to ensure reliable service discovery across all namespaces and prevent cross-namespace DNS resolution issues.
Fixes #1794
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.: