The Project | About Us | Contribute | Donations | License

HOME

In Kubernetes, health checks and probes are essential for ensuring that your applications are running smoothly and are healthy. They help Kubernetes determine the state of your application and take necessary actions if something goes wrong. This section will cover the different types of probes available in Kubernetes, how to configure them, and practical examples to help you understand their usage.

Types of Probes

Kubernetes supports three types of probes:

Liveness Probes: Determine if an application is running. If a liveness probe fails, Kubernetes will restart the container.
Readiness Probes: Determine if an application is ready to serve traffic. If a readiness probe fails, Kubernetes will remove the pod from the service's endpoints.
Startup Probes: Used to check if an application has started. If a startup probe fails, Kubernetes will kill the container and try to restart it.

Comparison Table

Probe Type	Purpose	Action on Failure
Liveness Probe	Checks if the application is running	Restarts the container
Readiness Probe	Checks if the application is ready to serve	Removes pod from service endpoints
Startup Probe	Checks if the application has started	Kills and restarts the container

Configuring Probes

Probes can be configured using three different methods:

HTTP Probes: Perform an HTTP GET request to check the health of the application.
TCP Probes: Perform a TCP check to ensure the application is listening on a specified port.
Command Probes: Execute a command inside the container to check its health.

HTTP Probe Example

apiVersion: v1
kind: Pod
metadata:
  name: http-probe-pod
spec:
  containers:
  - name: myapp
    image: myapp:latest
    livenessProbe:
      httpGet:
        path: /healthz
        port: 8080
      initialDelaySeconds: 3
      periodSeconds: 3

Explanation:

httpGet: Specifies the HTTP GET request to /healthz on port 8080.
initialDelaySeconds: The number of seconds after the container has started before the probe is initiated.
periodSeconds: How often (in seconds) to perform the probe.

TCP Probe Example

apiVersion: v1
kind: Pod
metadata:
  name: tcp-probe-pod
spec:
  containers:
  - name: myapp
    image: myapp:latest
    livenessProbe:
      tcpSocket:
        port: 8080
      initialDelaySeconds: 3
      periodSeconds: 3

Explanation:

tcpSocket: Specifies the TCP check on port 8080.

Command Probe Example

apiVersion: v1
kind: Pod
metadata:
  name: command-probe-pod
spec:
  containers:
  - name: myapp
    image: myapp:latest
    livenessProbe:
      exec:
        command:
        - cat
        - /tmp/healthy
      initialDelaySeconds: 3
      periodSeconds: 3

Explanation:

exec: Executes the command cat /tmp/healthy inside the container.

Practical Exercise

Exercise: Configure a Liveness and Readiness Probe

Create a YAML file named probe-example.yaml.
Define a pod with a container running an HTTP server.
Configure both liveness and readiness probes for the container.

Solution:

apiVersion: v1
kind: Pod
metadata:
  name: probe-example-pod
spec:
  containers:
  - name: myapp
    image: myapp:latest
    ports:
    - containerPort: 8080
    livenessProbe:
      httpGet:
        path: /healthz
        port: 8080
      initialDelaySeconds: 5
      periodSeconds: 5
    readinessProbe:
      httpGet:
        path: /ready
        port: 8080
      initialDelaySeconds: 5
      periodSeconds: 5

Explanation:

The livenessProbe checks the /healthz endpoint every 5 seconds after an initial delay of 5 seconds.
The readinessProbe checks the /ready endpoint every 5 seconds after an initial delay of 5 seconds.

Common Mistakes and Tips

Initial Delay: Ensure the initialDelaySeconds is sufficient for your application to start. If it's too short, the probe might fail before the application is ready.
Path and Port: Double-check the path and port in HTTP probes to ensure they match your application's configuration.
Command Probes: Ensure the command used in exec probes is available in the container and returns the expected result.

Conclusion

Health checks and probes are crucial for maintaining the reliability and availability of your applications in Kubernetes. By configuring liveness, readiness, and startup probes, you can ensure that your applications are running as expected and can handle traffic appropriately. In the next section, we will explore monitoring with Prometheus to gain insights into your application's performance and health.

Health Checks and Probes

Types of Probes

Comparison Table

Configuring Probes

HTTP Probe Example

TCP Probe Example

Command Probe Example

Practical Exercise

Exercise: Configure a Liveness and Readiness Probe

Common Mistakes and Tips

Conclusion

Kubernetes Course

Module 1: Introduction to Kubernetes

Module 2: Core Kubernetes Components

Module 3: Configuration and Secrets Management

Module 4: Networking in Kubernetes

Module 5: Storage in Kubernetes

Module 6: Advanced Kubernetes Concepts

Module 7: Monitoring and Logging

Module 8: Security in Kubernetes

Module 9: Scaling and Performance

Module 10: Kubernetes Ecosystem and Tools

Module 11: Case Studies and Real-World Applications

Module 12: Preparing for Kubernetes Certification