- Using Spring Admin + Eureka to monitor all micro-service and deploy it in Kubernetes;
- Spring Admin UI and discover all micro-service instances, but can't check detail of each instance, check detail network, we can see the service health check has show 502 error: http://[admin server real ip]/instances/3f5afb61f59b/actuator/health >> 502 bad getway
- Check Eureka register, I found all eureka client was resisted with Kubernetes virtual ip;
Asked
Active
Viewed 174 times
-2

Levi Li
- 1
- 1
1 Answers
0
I already resolve it, but change the dependency from spring-boot-admin to spring-cloud-admin

Levi Li
- 1
- 1