Skip to content

Load Test gRPC with SLOs

Load test a Kubernetes gRPC service and validate its service-level objectives (SLOs). This is a single-loop Kubernetes experiment.

Before you begin
  1. Try your first experiment. Understand the main concepts behind Iter8 experiments.
  2. Deploy the sample gRPC service in the Kubernetes cluster.
    kubectl create deploy hello --port=50051
    kubectl expose deploy hello --port=50051

Launch experiment

iter8 k launch \
--set "tasks={ready,grpc,assess}" \
--set ready.deploy=hello \
--set ready.service=hello \
--set ready.timeout=60s \
--set"hello.default:50051" \
--set"helloworld.Greeter.SayHello" \
--set grpc.protoURL="" \
--set assess.SLOs.upper.grpc/error-rate=0 \
--set assess.SLOs.upper.grpc/latency/mean=200 \
--set assess.SLOs.upper.grpc/latency/p'97\.5'=800 \
--set runner=job
About this experiment

This experiment consists of three tasks, namely, ready, grpc, and assess.

The ready task checks if the hello deployment exists and is available, and the hello service exists.

The grpc task sends call requests to the helloworld.Greeter.SayHello method of the cluster-local gRPC service with host address hello.default:50051, and collects Iter8's built-in gRPC load test metrics.

The assess task verifies if the app satisfies the specified SLOs: i) there are no errors, ii) the mean latency of the service does not exceed 50 msec, and iii) the 97.5th percentile latency does not exceed 200 msec.

This is a single-loop Kubernetes experiment where all the previously mentioned tasks will run once and the experiment will finish. Hence, its runner value is set to job.

Some variations and extensions of this experiment
  1. The grpc task can be configured with load related parameters such as the total number of requests, requests per second, or number of concurrent connections.
  2. The grpc task can be configured to JSON or binary data as payload. You can use this task to test unary or streaming gRPC methods.
  3. The assess task can be configured with SLOs for any of Iter8's built-in grpc load test metrics.
  4. This experiment can also be run in your local environment or run within a GitHub Actions pipeline.

Assert experiment outcomes, view experiment report, view experiment logs, and cleanup as described in your first experiment.


Remove the Iter8 experiment and the sample app from the Kubernetes cluster and the local Iter8 charts folder.

iter8 k delete
kubectl delete svc/hello
kubectl delete deploy/hello
rm -rf charts

Back to top