github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
k3s/test/images/logs-generator
History
Tim Hockin 3586986416 Switch to k8s.gcr.io vanity domain 
This is the 2nd attempt.  The previous was reverted while we figured out
the regional mirrors (oops).

New plan: k8s.gcr.io is a read-only facade that auto-detects your source
region (us, eu, or asia for now) and pulls from the closest.  To publish
an image, push k8s-staging.gcr.io and it will be synced to the regionals
automatically (similar to today).  For now the staging is an alias to
gcr.io/google_containers (the legacy URL).

When we move off of google-owned projects (working on it), then we just
do a one-time sync, and change the google-internal config, and nobody
outside should notice.

We can, in parallel, change the auto-sync into a manual sync - send a PR
to "promote" something from staging, and a bot activates it.  Nice and
visible, easy to keep track of.
 		2018-02-07 21:14:19 -08:00
..
BASEIMAGE
…
BUILD Autogenerate BUILD files 2017-12-23 13:12:11 -08:00
Dockerfile
…
Makefile
…
README.md Switch to k8s.gcr.io vanity domain 2018-02-07 21:14:19 -08:00
VERSION Fix review comments - luxas, ixdy 2017-06-30 18:51:23 +05:30
logs_generator.go
…

README.md

Logs Generator

Overview

Logs generator is a tool to create predictable load on the logs delivery system. Is generates random lines with predictable format and predictable average length. Each line can be later uniquely identified to ensure logs delivery.

Usage

Tool is parametrized with the total number of number that should be generated and the duration of the generation process. For example, if you want to create a throughput of 100 lines per second for a minute, you set total number of lines to 6000 and duration to 1 minute.

Parameters are passed through environment variables. There are no defaults, you should always set up container parameters. Total number of line is parametrized through env variable LOGS_GENERATOR_LINES_TOTAL and duration in go format is parametrized through env variable LOGS_GENERATOR_DURATION.

Inside the container all log lines are written to the stdout.

Each line is on average 100 bytes long and follows this pattern:

2000-12-31T12:59:59Z <id> <method> /api/v1/namespaces/<namespace>/endpoints/<random_string> <random_number>

Where <id> refers to the number from 0 to total_lines - 1, which is unique for each line in a given run of the container.

Image

Image is located in the public repository of Google Container Registry under the name

k8s.gcr.io/logs-generator:v0.1.1

Examples

docker run -i \
  -e "LOGS_GENERATOR_LINES_TOTAL=10" \
  -e "LOGS_GENERATOR_DURATION=1s" \
  k8s.gcr.io/logs-generator:v0.1.1

kubectl run logs-generator \
  --generator=run-pod/v1 \
  --image=k8s.gcr.io/logs-generator:v0.1.1 \
  --restart=Never \
  --env "LOGS_GENERATOR_LINES_TOTAL=1000" \
  --env "LOGS_GENERATOR_DURATION=1m"

Analytics