Health Checks

This section continues from the previous section - make sure you do the tutorial in sequence.
Service
Spring Boot Actuator
​Spring Boot Actuator can provide some basic health checking mechanisms via the /actuator/health endpoint. However, which endpoint you use depends on the Spring Boot version.
Spring Boot 2.3 and above, Spring Boot Actuator has dedicated support for Liveness Probe.
Spring Boot < 2.3 and below, it's best to create a simple endpoint that simply returns HTTP 200 response status instead of using the Spring Boot Actuator's /actuator/health endpoint. This is because /actuator/health by default may fail if an external dependency fails.
Spring Boot Version
Liveness Probe
Readiness Probe
>= 2.3
/actuator/health/liveness
/actuator/health/readiness
< 2.3
Any endpoint that simply returns 200
/actuator/health
Clone
1
git clone https://github.com/saturnism/jvm-helloworld-by-example
2
cd jvm-helloworld-by-example/helloworld-springboot-tomcat
Copied!
Add Dependencies
1
<project>
2
  ...
3
  <dependencies>
4
    <dependency>
5
      <groupId>org.springframework.boot</groupId>
6
      <artifactId>spring-boot-starter-actuator</artifactId>
7
    </dependency>
8
    
9
    ...
10
  </dependencies>
11
  ...
12
</project>
Copied!
Build
1
./mvnw package
Copied!
Containerize
Use Jib to containerize the application:
1
PROJECT_ID=$(gcloud config get-value project)
2
​
3
./mvnw compile com.google.cloud.tools:jib-maven-plugin:2.4.0:build \
4
  -Dimage=gcr.io/${PROJECT_ID}/helloworld
Copied!
Learn different ways to containerize a Java application in the Container Image section.
Liveness Probe
Kubernetes can automatically detect application issues using a Liveness Probe. When the Liveness Probe check fails, Kubernetes will automatically restart the container, in case restarting your application helps it to recover. If the container continues to fail the Liveness Probe, Kubernetes will go into a Crash Loop and backs off the restart exponentially.
Liveness Probe failure indicates to Kubernetes that the failure can be recovered after a restart.
If your Liveness Probe checks an endpoint that fails due to an external dependency, but the external dependency cannot recover simply because your container restarts, then it's not a good check! This type of checks may cause catastropic cascading failures.
k8s/deployment.yaml
1
apiVersion: apps/v1
2
kind: Deployment
3
metadata:
4
  labels:
5
    app: helloworld
6
  name: helloworld
7
spec:
8
  replicas: 1
9
  selector:
10
    matchLabels:
11
      app: helloworld
12
  template:
13
    metadata:
14
      labels:
15
        app: helloworld
16
    spec:
17
      containers:
18
      - image: gcr.io/.../helloworld
19
        name: helloworld
20
        resources:
21
          requests:
22
            cpu: 200m
23
            memory: 256Mi
24
          limits:
25
            cpu: 500m
26
            memory: 256Mi
27
        # Configure the liveness probe
28
        livenessProbe:
29
          httpGet:
30
            path: /actuator/health/liveness
31
            port: 8080
32
          initialDelaySeconds: 10
Copied!
In addition to httpGet, you can also configure different type of probes such as exec to execute a command to perform a non-HTTP check, or use tcpSocket to simply check if a port is listening. See Kubernetes Configure Liveness, Readiness, and Startup Probes documentation for more details.
Notice the additional initialDelaySeconds configuration. If your application starts slowly (e.g., 1 minute to start), and the livenessProbe starts the check early (e.g., 10 seconds), then the livenessProbe might never succeed - causing the application to always getting restarted.
When configuring a livenessProbe, always consider the initial delay needed for your application.
Readiness Probe
Even if your application is alive, it doesn't mean that it's ready to receive traffic. For example, during the startup, the application is alive, but it needs to pre-load data, or warmup caches, before it's ready to accept traffic. A Readiness Probe will let Kubernetes know when your application is ready to receive traffic, and only then will the instance be enlisted into the load balancer as a backend to serve requests (i.e., a Service's Endpoint).
k8s/deployment.yaml
1
apiVersion: apps/v1
2
kind: Deployment
3
metadata:
4
  labels:
5
    app: helloworld
6
  name: helloworld
7
spec:
8
  replicas: 1
9
  selector:
10
    matchLabels:
11
      app: helloworld
12
  template:
13
    metadata:
14
      labels:
15
        app: helloworld
16
    spec:
17
      containers:
18
      - image: gcr.io/.../helloworld
19
        name: helloworld
20
        resources:
21
          requests:
22
            cpu: 200m
23
            memory: 256Mi
24
          limits:
25
            cpu: 500m
26
            memory: 256Mi
27
        livenessProbe:
28
          httpGet:
29
            path: /actuator/health/liveness
30
            port: 8080
31
        # Configure the readiness probe
32
        readinessProbe:
33
          httpGet:
34
            path: /actuator/health/readiness
35
            port: 8080
Copied!
You should always configure a readinessProbe. Even if you don't use Spring Boot Actuator, you can point the probe to / or some endpoint that indicates the traffic is ready serve.
​

Service

Load Balancing

Last modified 1yr ago

Copy link

Contents