博客
关于我
k8s容器内部应用向eruaka注册ip问题
阅读量:287 次
发布时间:2019-03-01

本文共 1190 字,大约阅读时间需要 3 分钟。

springboot项目部署到k8s中,发现eruaka注册是容器id,这个其他应用是无法访问的

1
参考,现在pom.xml中添加:

org.springframework.cloud
spring-cloud-commons

接着使用${spring.cloud.client.ip-address}

eureka:  instance:    instance-id: ${   spring.cloud.client.ip-address}:    preferIpAddress: true    statusPageUrlPath: /actuator/info    healthCheckUrlPath: /actuator/health  client:    service-url:      defaultZone: http://192.168.5.207:8761/eureka/,http://192.168.5.180:8761/eureka/,http://192.168.5.154:8761/eureka/

确实替换为id了,但是确实容器IP,并不是主机IP,外部还是无法访问.

1
在k8s中设置spring.cloud.client.ip-addressk8s.port的环境变量,
1
在eruaka中看似是对的,点击链接打开的还是http://179.20.3.178:9010/actuator/info,依旧是容器ip和端口,
1
然而使用使用主机的IP和端口却可以访问.
1
这两者之前的不一致问题,怎么解决呢?如果了解k8s的网络模式,,解决办法就知道了。设置hostNetwork: true问题就解决了。就不用什么instance-id1
再看eruaka,就可以正常访问了
1
使用hostNetwork有弊端,会出现端口占用,故这里推荐使用下图的方式,使用EUREKA_INSTANCE_IP-ADDRESS环境变量即可,处理方式跟一致
1
当系统部署到生产环境,这里还有个dns的问题,你会发现docker内部无法访问域名

dnsConfig:        nameservers:          - 223.5.5.5`![1](https://img-blog.csdnimg.cn/20200724171135366.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L3dhcnJhaA==,size_16,color_FFFFFF,t_70)``

转载地址:http://ktwo.baihongyu.com/

你可能感兴趣的文章
No Datastore Session bound to thread, and configuration does not allow creation of non-transactional
查看>>
No fallbackFactory instance of type class com.ruoyi---SpringCloud Alibaba_若依微服务框架改造---工作笔记005
查看>>
No Feign Client for loadBalancing defined. Did you forget to include spring-cloud-starter-loadbalanc
查看>>
No mapping found for HTTP request with URI [/...] in DispatcherServlet with name ...的解决方法
查看>>
No mapping found for HTTP request with URI [/logout.do] in DispatcherServlet with name 'springmvc'
查看>>
No module named 'crispy_forms'等使用pycharm开发
查看>>
No module named 'pandads'
查看>>
No module named cv2
查看>>
No module named tensorboard.main在安装tensorboardX的时候遇到的问题
查看>>
No module named ‘MySQLdb‘错误解决No module named ‘MySQLdb‘错误解决
查看>>
No new migrations found. Your system is up-to-date.
查看>>
No qualifying bean of type XXX found for dependency XXX.
查看>>
No qualifying bean of type ‘com.netflix.discovery.AbstractDiscoveryClientOptionalArgs<?>‘ available
查看>>
No resource identifier found for attribute 'srcCompat' in package的解决办法
查看>>
no session found for current thread
查看>>
No static resource favicon.ico.
查看>>
no such file or directory AndroidManifest.xml
查看>>
No toolchains found in the NDK toolchains folder for ABI with prefix: mips64el-linux-android
查看>>
NO.23 ZenTaoPHP目录结构
查看>>
no1
查看>>