lynx-runner binary runs on your infrastructure and connects to the Lynx platform. You can deploy it on bare metal, VMs, or Kubernetes.
Connection credentials (endpoint URL and auth tokens) are provided during onboarding. Set them as environment variables before starting the runner.
Start a runner
Flags
| Flag | Description |
|---|---|
--runner-id | Unique identifier for this runner. Must be distinct across your pool. |
--name | Display name shown in the API and dashboard |
--max-concurrent-jobs | Maximum number of jobs this runner executes in parallel |
--heartbeat-interval-secs | How frequently the runner sends a heartbeat (default: 5) |
Verify registration
After starting, confirm the runner has registered:"status": "Idle". Inspect a specific runner:
Running multiple runners
Start additional runners with distinct--runner-id values. Lynx distributes jobs across all active runners automatically.
Drain before maintenance
Before taking a runner offline, drain it so it finishes its current jobs and stops accepting new ones:Maintenance. Resume when ready:
Kubernetes deployment
Runlynx-runner as a Deployment. Each pod acts as one runner in the pool.
lynx-credentials secret. Contact Tetryx for your onboarding credentials.