1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
I believe you are encountering the same issue as described in this CoreDNS issue - https://github.com/coredns/coredns/issues/2159
As per this comment, your desired setup will work only if the FQDN of the ETCD server can be resolved outside the cluster.
The work-around is to directly specify the ClusterIP of your ETCD service in the Corefile endpoint configuration, and I see that you are already using this approach.
The bottom line is that your CoreDNS pod cannot use itself to perform DNS resolution.
I hope this helps!
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a 2 mois
- demandé il y a 2 mois
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 6 mois
- AWS OFFICIELA mis à jour il y a un an