Open lucasobsidiam opened 4 years ago
I'm not sure why amiCount
isn't populated, but it would probably be as simple as providing a default.
Is there a simple way of doing that without modifying source code? To temporarily show the connected micro-services properly.
Not that I know of. You could copy the template into your local app's src/main/resources/templates/eureka/status.ftlh
and it should find that first.
Is there any elegant solution for this by now? @lucasobsidiam @spencergibb
+1 facing same issue when deployed service on kubernetes
any update on this?
no, there isn't
I've successfully connected one of our microservices to Eureka using Fargate. Eureka is currently on an actual EC2 instance and microservices will be running from Fargate (hopefully Eureka too if I manage to get it to work). I have already got this running properly (or it seems as microservices connect to Eureka), with that said, I am getting a FreeMarker template error on the Eureka status page under the AMIs columns in "Instances currently registered with Eureka".
What I have done to achieve this Fargate to EC2 Eureka connection with private IP is the following. This dockerfile loads an entrypoint file which runs a shell script.
Dockerfile:
This entrypoint shell script saves the private IP from the Fargate metadata endpoint into the shell session. entrypoint.sh:
The application property file loads the Fargate private IP so the microservice connects successfully. application-aws.properties
This is the error I receive on the Eureka page under the AMIs column even though the services seem to work. Any ideas?