使用Minikube和Kompose从Docker转Kubernetes后Eureka服务发现异常

我使用Kompose工具将Docker-compose.yml文件转换为适用于Minikube的Kubernetes配置。转换完成后，Eureka注册中心虽能在8761端口正常访问，但无法发现任何微服务，而此前使用Docker Compose部署时一切正常。以下是discovery-service和login-service转换前后的配置对比：

转换前（docker-compose.yml） #

discovery-service #

discovery-service:
    build: ./discovery-service
    image: springcloud/eureka:latest
    container_name: eureka-discovery-server-container
    ports:
      - "8761:8761"
    environment:
        spring.config.import-check.enabled: false

    networks:
        microservices_network:
            aliases:
                - discovery-service-container
                - eureka-discovery-server-container
                - discovery-service

login-service #

login-service:
    container_name: login-service-container
    image: springboot-app-login
    restart: always
    build: ./login-service
    ports:
      - "8083:8080"
    depends_on:
      login-db-docker-image:
        condition: service_healthy
      discovery-service:
        condition: service_started
    networks:
        - microservices_network

转换后Kubernetes配置 #

discovery-service-deployment.yml #

apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
    kompose.cmd: C:\ProgramData\chocolatey\lib\kubernetes-kompose\tools\kompose.exe convert -f docker-compose.yml
    kompose.version: 1.28.0 (c4137012e)
  creationTimestamp: null
  labels:
    io.kompose.service: discovery-service
  name: discovery-service
spec:
  replicas: 1
  selector:
    matchLabels:
      io.kompose.service: discovery-service
  strategy: {}
  template:
    metadata:
      annotations:
        kompose.cmd: C:\ProgramData\chocolatey\lib\kubernetes-kompose\tools\kompose.exe convert -f docker-compose.yml
        kompose.version: 1.28.0 (c4137012e)
      creationTimestamp: null
      labels:
        io.kompose.network/microservices-kubernetes-microservices-network: "true"
        io.kompose.service: discovery-service
    spec:
      containers:
        - env:
            - name: spring.config.import-check.enabled
              value: "false"
          image: springcloud/eureka:latest
          name: eureka-discovery-server-container
          ports:
            - containerPort: 8761
          resources: {}
      restartPolicy: Always
status: {}

discovery-service-service.yml #

apiVersion: v1
kind: Service
metadata:
  annotations:
    kompose.cmd: C:\ProgramData\chocolatey\lib\kubernetes-kompose\tools\kompose.exe convert -f docker-compose.yml
    kompose.version: 1.28.0 (c4137012e)
  creationTimestamp: null
  labels:
    io.kompose.service: discovery-service
  name: discovery-service
spec:
  ports:
    - name: "8761"
      port: 8761
      targetPort: 8761
  selector:
    io.kompose.service: discovery-service
status:
  loadBalancer: {}

login-service-deployment.yml #

apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
    kompose.cmd: C:\ProgramData\chocolatey\lib\kubernetes-kompose\tools\kompose.exe convert -f docker-compose.yml
    kompose.version: 1.28.0 (c4137012e)
  creationTimestamp: null
  labels:
    io.kompose.service: login-service
  name: login-service
spec:
  replicas: 1
  selector:
    matchLabels:
      io.kompose.service: login-service
  strategy: {}
  template:
    metadata:
      annotations:
        kompose.cmd: C:\ProgramData\chocolatey\lib\kubernetes-kompose\tools\kompose.exe convert -f docker-compose.yml
        kompose.version: 1.28.0 (c4137012e)
      creationTimestamp: null
      labels:
        io.kompose.network/microservices-kubernetes-microservices-network: "true"
        io.kompose.service: login-service
    spec:
      containers:
        - image: springboot-app-login
          name: login-service-container
          ports:
            - containerPort: 8080
          resources: {}
      restartPolicy: Always
status: {}

login-service-service.yml #

apiVersion: v1
kind: Service
metadata:
  annotations:
    kompose.cmd: C:\ProgramData\chocolatey\lib\kubernetes-kompose\tools\kompose.exe convert -f docker-compose.yml
    kompose.version: 1.28.0 (c4137012e)
  creationTimestamp: null
  labels:
    io.kompose.service: login-service
  name: login-service
spec:
  ports:
    - name: "8083"
      port: 8083
      targetPort: 8080
  selector:
    io.kompose.service: login-service
status:
  loadBalancer: {}

原因分析 #

1. 微服务缺失Eureka注册配置：Docker Compose环境中，微服务可通过容器别名自动发现Eureka，但Kompose转换时未将微服务的Eureka注册配置同步到K8s Deployment中。login-service容器未收到Eureka服务地址配置，无法发起注册请求。
2. 依赖关系未正确转换：Docker Compose的depends_on仅保证启动顺序，但K8s中Kompose未将其转换为就绪探针或启动依赖逻辑。login-service可能在Eureka完全初始化前就启动，注册失败后无重试机制，导致无法完成注册。
3. 网络访问配置不匹配：虽然K8s创建了discovery-service的Service，但需确认微服务是否使用正确的Service名称（discovery-service）访问Eureka。若微服务原配置使用Docker Compose容器别名，需调整为K8s Service名称。

解决建议 #

• 添加Eureka注册环境变量：在login-service的Deployment容器配置中添加Eureka地址的环境变量，示例：

  spec:
    containers:
      - image: springboot-app-login
        name: login-service-container
        ports:
          - containerPort: 8080
        env:
          - name: EUREKA_CLIENT_SERVICEURL_DEFAULTZONE
            value: "http://discovery-service:8761/eureka/"
          # 可选：开启IP注册，避免DNS解析问题
          - name: EUREKA_INSTANCE_PREFER_IP_ADDRESS
            value: "true"
  

• 配置就绪探针与重试机制：给login-service添加就绪探针，确保Eureka可用后再对外提供服务；同时在微服务的Spring配置中添加注册重试逻辑：

  # application.yml 示例
  eureka:
    client:
      register-with-eureka: true
      fetch-registry: true
      service-url:
        defaultZone: http://discovery-service:8761/eureka/
      retry:
        enabled: true
        initial-interval-seconds: 5
        max-interval-seconds: 20
        multiplier: 1.5
  

• 验证内部网络连通性：使用kubectl exec进入login-service容器，执行curl http://discovery-service:8761确认能访问Eureka，排除网络问题：

  kubectl exec -it <login-service-pod-name> -- curl http://discovery-service:8761
  

• 检查日志定位问题：查看Eureka和login-service的日志，确认是否有注册失败的错误信息：

  kubectl logs <discovery-service-pod-name>
  kubectl logs <login-service-pod-name>
  

内容的提问来源于stack exchange，提问作者brohjoe