Eureka can't resolve dns in kubernetes

jhipster / jhipster-registry

JHipster Registry, based on Spring Cloud Netflix Eureka and Spring Cloud Config

Apache License 2.0

698 stars 657 forks source link

Eureka can't resolve dns in kubernetes #521

Closed greggameplayer closed 2 years ago

greggameplayer commented 2 years ago

Overview of the issue

I get this error every minute which said that there is a problem in the dns resolving.

In the jhipster-registry-0 pod it bugs on jhipster-registry-1 dns and in the jhipster-registry-1 pod it bugs on jhipster-registry-0 dns.

JHipster Registry Version(s)

7.1.0

renanfranca commented 2 years ago

@greggameplayer hello! I'm using Google cloud and I didn't face this error. I run locally with minikube and it works too

greggameplayer commented 2 years ago

Ok i've corrected it, it was just because in the generated jhipster-registry service, the port was named but on the container it wasn't named so i've put targetPort: instead of name in the service