ETCD dns-check Init-container is failing.

[Pavan976]

Hello Team,

I'm trying to integrate external dns with coredns but etcd pods are not coming up the, init-container for dns-check is failing. could you please ?

error:

Server: 10.247.3.10 Address 1: 10.247.3.10 coredns.kube-system.svc.cluster.local

nslookup: can't resolve 'example-etcd-cluster-2qp827qg7z.example-etcd-cluster.default.svc' Server: 10.247.3.10 Address 1: 10.247.3.10 coredns.kube-system.svc.cluster.local

nslookup: can't resolve 'example-etcd-cluster-2qp827qg7z.example-etcd-cluster.default.svc' nslookup: can't resolve 'example-etcd-cluster-2qp827qg7z.example-etcd-cluster.default.svc' Server: 10.247.3.10 Address 1: 10.247.3.10 coredns.kube-system.svc.cluster.local

Server: 10.247.3.10 Address 1: 10.247.3.10 coredns.kube-system.svc.cluster.local

nslookup: can't resolve 'example-etcd-cluster-2qp827qg7z.example-etcd-cluster.default.svc' nslookup: can't resolve 'example-etcd-cluster-2qp827qg7z.example-etcd-cluster.default.svc' Server: 10.247.3.10 Address 1: 10.247.3.10 coredns.kube-system.svc.cluster.local

nslookup: can't resolve 'example-etcd-cluster-2qp827qg7z.example-etcd-cluster.default.svc' Server: 10.247.3.10 Address 1: 10.247.3.10 coredns.kube-system.svc.cluster.local

[kundan2707]

/assign

[kundan2707]

@Pavan976 can you share all steps with which you are tryig to integrate external dns with coredns ?

[Pavan976]

Hello @kundan2707,

Note: We are using cloud provided service (huwaei cloud) for kubernetes and masters are managed by huwaei. and we have installed coredns addons when we create cluster.

The link which i followed: https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/coredns.md

1. have deployed etcd-op
2. etcd deployment, the init container is failing because of dns check(previously pasted error) :: kubectl apply -f https://raw.githubusercontent.com/coreos/etcd-operator/HEAD/example/example-etcd-cluster.yaml
3. installed core_dns with configuration : wget https://raw.githubusercontent.com/helm/charts/HEAD/stable/coredns/values.yaml

  - name: etcd
    parameters: example.org
    configBlock: |-
      stubzones
      path /skydns
      endpoint http://10.105.68.165:2379

4. installed external dns with etcd url.

[kundan2707]

@Pavan976 I am trying to reproduce this issue with steps you mentioned above and will update you very soon.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[kundan2707]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.