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

When deploying to k8s - there are excessise DNS requests. #1626

Open
gecube opened this issue Oct 23, 2024 · 1 comment
Open

When deploying to k8s - there are excessise DNS requests. #1626

gecube opened this issue Oct 23, 2024 · 1 comment

Comments

@gecube
Copy link

gecube commented Oct 23, 2024

Good day!

The frest installation EKS + latest victoria k8s metrics stack.

In parallel the coroot solution is installed.

I am observing the next

telegram-cloud-photo-size-2-5242590837488084421-y

It is the excessive DNS requests from victoria metrics agent to different non-existing domain names in the cluster like:

  • vmsingle-victoria-metrics-k8s-stack.monitoring-system.svc.svc.cluster.local
  • vmsingle-victoria-metrics-k8s-stack.monitoring-system.svc.monitoring-system.svc.cluster.local

I am asking to improve the default settings of agent to point to vmsingle-victoria-metrics-k8s-stack.monitoring-system.svc.cluster.local. (with dot on the end) effectively eliminating extra DNS requests. Probably it is the best solution. The only drawback that then we need to put a cluster TLD (cluster.local) as a value in helm chart. But it is ok for many operators (FluxCD, altinity operator and others have the same setting).

@AndrewChubatiuk
Copy link
Contributor

will be fixed as soon as #1455 is fixed

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

No branches or pull requests

2 participants