Skip to content

Latest commit

 

History

History
194 lines (140 loc) · 5.63 KB

README.md

File metadata and controls

194 lines (140 loc) · 5.63 KB
Raw

Testing Environment

Requirements

  • docker v24+

Setup

Clone the project

git clone https://github.com/Kuadrant/limitador.git
cd limitador/limitador-server/sandbox

Check out make help for all the targets.

Deployment options

Limitador's configuration Command Info
In-memory configuration make deploy-in-memory Counters are held in Limitador (ephemeral)
Redis make deploy-redis Uses Redis to store counters
Redis Secured make deploy-redis-tls Uses Redis with TLS and password protected to store counters
Redis Cached make deploy-redis-cached Uses Redis to store counters, with an in-memory cache
Redis Otel Instrumented make deploy-redis-otel Uses redis to store counters, instrumented with opentelemetry
Disk make deploy-disk Uses disk to store counters
Distributed make deploy-distributed Counters are held in Limitador (ephemeral) but replicated to other Limitador servers.

| Distributed 3 Node | make deploy-distributed-3-node | Counters are held in Limitador (ephemeral) but replicated to 3 other Limitador servers. |

Running Multi Node Distributed Deployments

The make deploy-distributed target can be connected to other Limitador servers but requires you to set the PEER_ID and PEER_URLS environment variables when you run the target.

If you have 3 servers you want to replicate between, you would run the following commands:

# on server where: hostname=server1
PEER_ID=`hostname` PEER_URLS="http://server2:15001 http://server3:15001" make deploy-distributed
# on server where: hostname=server2
PEER_ID=`hostname` PEER_URLS="http://server1:15001 http://server3:15001" make deploy-distributed
# on server where: hostname=server3
PEER_ID=`hostname` PEER_URLS="http://server1:15001 http://server2:15001" make deploy-distributed

The PEER_ID just need to be unique between the servers, and the PEER_URLS should be a space-separated list of the other servers' URLs.

Limitador's admin HTTP endpoint

Limits

curl -i http://127.0.0.1:18080/limits/test_namespace

Counters

curl -i http://127.0.0.1:18080/counters/test_namespace

Metrics

curl -i http://127.0.0.1:18080/metrics

Limitador's GRPC RateLimitService endpoint

Get grpcurl. You need Go SDK installed.

Golang version >= 1.18 (from fullstorydev/grpcurl)

make grpcurl

Inspect RateLimitService GRPC service

bin/grpcurl -plaintext 127.0.0.1:18081 describe envoy.service.ratelimit.v3.RateLimitService

Make a custom request

bin/grpcurl -plaintext -d @ 127.0.0.1:18081 envoy.service.ratelimit.v3.RateLimitService.ShouldRateLimit <<EOM
{
    "domain": "test_namespace",
    "hits_addend": 1,
    "descriptors": [
        {
            "entries": [
                {
                    "key": "req.method",
                    "value": "POST"
                },
                {
                    "key": "req.path",
                    "value": "/"
                }
            ]
        }
    ]
}
EOM

Do repeated requests. As the limit is set to max 5 request for 60 seconds, you should see OVER_LIMIT response after 5 requests.

while :; do bin/grpcurl -plaintext -d @ 127.0.0.1:18081 envoy.service.ratelimit.v3.RateLimitService.ShouldRateLimit <<EOM; sleep 1; done
{
    "domain": "test_namespace",
    "hits_addend": 1,
    "descriptors": [
        {
            "entries": [
                {
                    "key": "req.method",
                    "value": "POST"
                },
                {
                    "key": "req.path",
                    "value": "/"
                }
            ]
        }
    ]
}
EOM

Downstream traffic

Upstream service implemented by httpbin.org

curl -i -H "Host: example.com" http://127.0.0.1:18000/get

Load Testing the GRPC RateLimitService directly

This load test will use grpcurl. You need Go SDK installed.

Run a load test a 5000 requests per second (RPS) for 10 seconds:

RPS=5000 make load-test

Load Testing via Envoy Proxy

cargo run --manifest-path loadtest/Cargo.toml  --package loadtest --release -- --report-file=report.htm

The report will be saved in report.htm file.

Limitador Image

By default, the sandbox will run Limitador's limitador-testing:latest image.

Building limitador-testing:latest image

You can easily build the limitador's image from the current workspace code base with:

make build

The image will be tagged with limitador-testing:latest

Using custom Limitador's image

The LIMITADOR_IMAGE environment variable overrides the default image. For example:

make deploy-in-memory LIMITADOR_IMAGE=quay.io/kuadrant/limitador:latest

Clean env

make clean