Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(logagent): correct dns policy for logagent daemonset #2256

Merged
merged 1 commit into from
Mar 31, 2023

Conversation

zhangzhangzf
Copy link
Collaborator

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:

/kind bug

What this PR does / why we need it:
The logagent has enabled hostNetwork, and the DNS policy is Clusterfirst. During domain name resolution, the pod inherits the domain name resolution configuration of the node, resulting in the inability to resolve domain names through kube-dns. The elasticsearch domain name resolution within the cluster fails. We need to modify the domain name resolution policy of the logagent to ClusterFirstWithHostNet.
Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:


Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@zhangzhangzf zhangzhangzf requested a review from choujimmy as a code owner March 31, 2023 08:08
@huxiaoliang huxiaoliang merged commit 8147a11 into tkestack:master Mar 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants