如何将Eureka Server地址传递给Kubernetes中的Config Server Pod

Let's walk through three practical, actionable approaches to solve this problem—from quick testing fixes to Kubernetes-native best practices that'll make your setup more reliable:

1. Directly Inject Environment Variables via kubectl run #

This is the fastest way for one-off deployments or testing. You can pass the Eureka address as an environment variable directly when starting your Config Server Pod:

kubectl run config-server --image=config-server-image --port=8888 \
  --env EUREKA_SERVER_URL=http://172.16.100.81:31000

In your Spring Boot Config Server app, reference this variable in your configuration file to point to Eureka:

# application.yml
eureka:
  client:
    service-url:
      defaultZone: ${EUREKA_SERVER_URL}/eureka/

Or use @Value("${EUREKA_SERVER_URL}") in your Java code if you need to access it programmatically.

2. Use a Kubernetes ConfigMap for Reusable Configuration #

If you want to manage this configuration separately (or reuse it across multiple pods), a ConfigMap is the way to go:

First, create a ConfigMap storing your Eureka server URL:

kubectl create configmap eureka-service-config \
  --from-literal=eureka.server.url=http://172.16.100.81:31000

Then start your Config Server Pod and inject the ConfigMap values as environment variables:

kubectl run config-server --image=config-server-image --port=8888 \
  --env-from=configmap/eureka-service-config

For even more flexibility, you can mount the ConfigMap as a configuration file directly into Spring Boot's default config directory (/config), which the app will automatically load:

kubectl run config-server --image=config-server-image --port=8888 \
  --volume name=eureka-config,configmap=eureka-service-config \
  --volume mount=name=eureka-config,mount-path=/config

Just make sure your ConfigMap includes a properly formatted properties/yaml file (use --from-file instead of --from-literal if you're loading a local config file).

3. Use Kubernetes Service DNS (Recommended for Internal Communication) #

Here's a pro tip: you don't need to use the NodePort IP for cluster-internal communication! Kubernetes automatically assigns DNS names to Services, so your Config Server can reach Eureka using the Service name directly.

Since you already exposed Eureka with kubectl expose deployment eureka-server --type NodePort --port=8761 --node-port=31000, the Service name eureka-server is resolvable within the cluster. That means you can set the environment variable to:

kubectl run config-server --image=config-server-image --port=8888 \
  --env EUREKA_SERVER_URL=http://eureka-server:8761

This approach is way more reliable than hardcoding a node IP because:

• If your Eureka Pod restarts or gets rescheduled, the Service DNS will automatically point to the new Pod IP.
• You avoid tying your setup to a specific node's IP address.
• It aligns with Kubernetes' built-in service discovery patterns.

Update your Spring Boot config to use this URL just like before:

# application.properties
eureka.client.service-url.defaultZone=${EUREKA_SERVER_URL}/eureka/

Bonus: Clean Up Unnecessary NodePorts #

If you don't need external access to Eureka or Config Server, switch their Service type to ClusterIP (the default) instead of NodePort—this keeps services internal to the cluster and reduces unnecessary exposure:

kubectl expose deployment eureka-server --port=8761
kubectl expose deployment config-server --port=8888

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