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

DNS Resolver : The name to resolve is too specific. #6006

Closed
treussart opened this issue Apr 24, 2022 · 3 comments
Closed

DNS Resolver : The name to resolve is too specific. #6006

treussart opened this issue Apr 24, 2022 · 3 comments

Comments

@treussart
Copy link

Describe the bug
Into the file:

dns_resolver: 'kube-dns.kube-system.svc.cluster.local',

The pod is crashloopbackoff because it cannot resolve the name: kube-dns.kube-system.svc.cluster.local

On my k8s cluster the name is coredns instead of kube-dns.

For resolve this issue, I created a new service with the same spec than coredns, but I think we should be able to change it in the Helm chart config.

To Reproduce
Steps to reproduce the behavior:

  1. Rename the service to something other than kube-dns
  2. Install the chart grafana/loki-simple-scalable

Expected behavior
A crashloopbackoff of the pods loki-simple-scalable-*

Environment:

  • Infrastructure: Kubernetes
  • Deployment tool: helm
@nktl
Copy link

nktl commented May 6, 2022

Same problem here on RedHat OpenShift - it uses CoreDNS and kube-dns.kube-system.svc.cluster.local does not exist there.

@irizzant
Copy link
Contributor

This is configurable through the chart options

@erSitzt
Copy link

erSitzt commented Sep 9, 2022

Just for anyone who might stumble upon this..

RKE2 Cluster

global:
  clusterDomain: cluster.local
  dnsNamespace: kube-system
  dnsService: rke2-coredns-rke2-coredns

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

4 participants