By default, Eureka and Config Server are used to use Config First boot. Essentially, you make the eureka server a configuration server client, but you do not make the configuration server the eureka client.
As David Sier said to these (and this ), the creator of the spring cloud, you must use a configuration server with a front-end load balancer, so one URL is already available.
I am also new to spring Cloud, but I agree with him, since Eureka is a service discovery, IMHO it should only work on this problem domain. This would create complex logic for Eureka servers that request configuration servers for configuration. I cannot imagine how the Eureka server finds out which configuration server to get if Config Server is also an Eureka server to get its defaultZone list.
It would be much easier for me to separate Config Server HA.
source
share