Difficulty: Beginner
Estimated Time: 10 minutes

In this scenario, you will learn how to add a health check that will check if a service within the cluster is available to receive traffic or not. With a health check enabled, if a service crashes then Envoy will stop sending traffic. Also you will learn how to configure Outlier Detection to eject hosts based on the responses from real requests.

You will learn how to:

  • Add a HTTP health check / Outlier Detection.

  • Test load balancing options when a service is unavailable.

  • Ensure how to continue to deliver successful requests when services are unavailable.

Congratulations! You successfully added health checks to your cluster configuration to ensure that users have the best experience possible!

In this sceanario, you learned how to:

  • Add a HTTP health check / Outlier Detection.

  • Test load balancing options when a service is unavailable.

  • Ensure how to continue to deliver successful requests when services are unavailable.

Detecting Unavailable Services Using health checks and outlier detection

Step 1 of 8

Step 1 - Proxy Configuration

An initial envoy configuration file has been created at envoy.yaml

This is configured to proxy all incoming requests for any domain to 172.18.0.3 and 172.18.0.4.

However, at the moment, if 172.18.0.3 went down then Envoy would still continue to deliver traffic to the service. As a result, users would have a degraded experience and encounter errors.

Instead, we want Envoy to automatically detect that the service is unavailable and remove it from the load balancer rotation. This is done by adding health checks to the cluster which will be defined in the next step.