Install eureka in kubernetes

by | Sep 25, 2024 | Technology

To install Eureka (a service discovery tool from Netflix, commonly used in microservices architectures) in a Kubernetes cluster, you can deploy a Eureka server using a Kubernetes deployment and service configuration. Here’s a step-by-step guide to installing and configuring Eureka in Kubernetes.

Prerequisites:

  • A running Kubernetes cluster.
  • kubectl installed and configured to access your Kubernetes cluster.
  • A Docker image of Eureka (or you can use a publicly available image like springcloud/eureka).

Step 1: Create a Eureka Docker Image

If you don’t have your own Docker image for Eureka, you can use the springcloud/eureka image from Docker Hub or build your own with Spring Cloud Eureka.

If you want to create your own image:

  1. Set up a Spring Boot project that includes the Eureka Server.
  2. Build the image and push it to a Docker registry.
dockerfile
FROM openjdk:8-jre-alpine
ADD target/eureka-server.jar /usr/local/lib/eureka-server.jar
ENTRYPOINT ["java", "-jar", "/usr/local/lib/eureka-server.jar"]

If you don’t want to build an image, you can use springcloud/eureka.

Step 2: Create a Kubernetes Deployment for Eureka

Create a YAML configuration for a Eureka deployment. This will define how many replicas of the Eureka server you want to run and the Docker image you are using.

yaml
# eureka-deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: eureka-server
labels:
app: eureka-server
spec:
replicas: 1
selector:
matchLabels:
app: eureka-server
template:
metadata:
labels:
app: eureka-server
spec:
containers:
- name: eureka-server
image: springcloud/eureka:latest # You can replace this with your own Eureka image
ports:
- containerPort: 8761
env:
- name: EUREKA_CLIENT_REGISTER_WITH_EUREKA
value: "false"
- name: EUREKA_CLIENT_FETCH_REGISTRY
value: "false"
- name: EUREKA_SERVER_WAIT_TIME_IN_MS
value: "5000"
- name: EUREKA_INSTANCE_HOSTNAME
valueFrom:
fieldRef:
fieldPath: status.hostIP
readinessProbe:
httpGet:
path: /eureka/apps
port: 8761
initialDelaySeconds: 30
timeoutSeconds: 10
periodSeconds: 10

Step 3: Create a Kubernetes Service for Eureka

You’ll need a service to expose Eureka to the rest of your Kubernetes cluster or to external clients. This can be a ClusterIP service (for internal access) or a LoadBalancer (if you want it accessible externally).

yaml
# eureka-service.yaml
apiVersion: v1
kind: Service
metadata:
name: eureka-service
labels:
app: eureka-server
spec:
ports:
- port: 8761
targetPort: 8761
selector:
app: eureka-server
type: ClusterIP # Change to LoadBalancer if you need external access

Step 4: Deploy Eureka to Kubernetes

  1. Apply the deployment and service configurations:
bash
kubectl apply -f eureka-deployment.yaml
kubectl apply -f eureka-service.yaml
  1. Verify that the Eureka server is running:
bash
kubectl get pods

This will show the status of the Eureka pod. Once the pod is in the Running state, Eureka is deployed.

  1. If you used ClusterIP, you can access Eureka inside the cluster by using the service name, eureka-service.
  2. If you used LoadBalancer, you can find the external IP to access Eureka by running:
bash
kubectl get services

Once you get the external IP, you can access the Eureka dashboard by navigating to http://<EXTERNAL-IP>:8761.

Step 5: Configure Eureka Clients

You can configure your microservices to register with Eureka by updating their Spring Boot configuration or other service discovery configurations.

For Spring Boot applications, add the following in the application.properties or application.yml:

properties
eureka.client.serviceUrl.defaultZone=http://eureka-service:8761/eureka

This ensures that your services register with the Eureka server running on Kubernetes.

Step 6: Scaling Eureka (Optional)

If you want to run Eureka in a highly available mode, you can increase the replicas in your deployment configuration. You would also need to configure Eureka to run in a peer-aware mode, which involves updating the Eureka server configuration to point to other Eureka instances.

You can modify the replicas value in eureka-deployment.yaml:

yaml
replicas: 3

Then, configure each Eureka instance to be aware of its peers:

properties
eureka.client.serviceUrl.defaultZone=http://eureka-service-1:8761/eureka,http://eureka-service-2:8761/eureka,http://eureka-service-3:8761/eureka

This configuration will allow Eureka instances to synchronize with each other.

×
Sign in
Sign up

Sign In

Sign Up