Skip to content
ICATraffic ManagementSingle nodeMedium

Locality failover with outlier detection

Scenario ica-trf-007 · about 7 minutes · 7 points · 4 grader checks

Configure locality-aware load balancing that fails over from one region to another when endpoints are ejected.

  • locality-load-balancing
  • failover
  • outlier-detection
  • destinationrule
  • traffic-management

What you will practise

  • Configure localityLbSetting failover in a DestinationRule
  • Combine failover with the outlier detection it depends on
  • Inspect the programmed cluster with istioctl proxy-config

Start this lab

With the CLI installed and signed in, this command provisions a single node cluster on your Mac, applies the scenario setup and prints the task below.

goldenkube start ica-trf-007

Task

The task text exactly as the CLI shows it. Solve it on the cluster, then run goldenkube submit.

Istio is installed. The node exam-cp1 is labelled with topology.kubernetes.io/region=eu-west. Namespace "travel" (in the mesh) runs the Service "catalog" (port 8000) and the Deployment "curl". Create a DestinationRule "catalog" in "travel" for the host "catalog" so that: 1. locality load balancing is enabled and traffic from region "eu-west" fails over to region "eu-central" when no healthy endpoint is left in eu-west; 2. a host is ejected after 1 consecutive 5xx error, analysed every 5 seconds, for a base ejection time of 30 seconds. Requests from "curl" to "catalog" must keep working.

Requirements and details

Certification
ICA · Istio Certified Associate
Domain
Traffic Management
Difficulty
Medium
Cluster topology
Single node
Cluster features
None beyond the base cluster
Recommended time
7 minutes
Points
7
Grader checks
4
Kubernetes version
1.35
Minimum CLI version
0.1.0
Scenario version
1
Published

Grading runs locally: 4 state checks read your cluster when you submit; the scenario passes when every check passes. Hints, the reference solution and the check definitions are available only inside the CLI, not on this page.

Install the CLICreate a free account

More Traffic Management labs

ICATraffic ManagementEasy

Expose a service through the ingress gateway

Publish an in-mesh HTTP service on a host name through the Istio ingress gateway with a Gateway and a VirtualService.

Single node · ~7 min · 7 points

  • gateway
  • virtualservice
  • ingress
  • traffic-management

goldenkube start ica-trf-001

ICATraffic ManagementMedium

Route requests by header to a service version

Define service subsets and send requests of one user to v2 while everybody else stays on v1.

Single node · ~8 min · 8 points

  • virtualservice
  • destinationrule
  • subsets
  • header-routing
  • traffic-management

goldenkube start ica-trf-002

ICATraffic ManagementEasy

Shift 20 percent of traffic to a new version

Split traffic between two versions of a service with weighted routes.

Single node · ~7 min · 6 points

  • traffic-shifting
  • weights
  • virtualservice
  • destinationrule
  • traffic-management

goldenkube start ica-trf-003

ICATraffic ManagementMedium

Lock down egress and register one external host

Switch the mesh to registry-only outbound traffic and allow exactly one external host with a ServiceEntry.

Single node · ~9 min · 9 points

  • egress
  • serviceentry
  • outbound-traffic-policy
  • meshconfig
  • traffic-management

goldenkube start ica-trf-004

Independent community project, not affiliated with or endorsed by CNCF or The Linux Foundation. Lab results are practice feedback, not an exam score.