See how LoadStrike docs cover coordinator and agent execution, Docker images, and EKS-oriented cluster guidance.
The docs already cover the coordinator and agent runtime model, NATS-backed distributed execution, and a Docker and EKS-focused setup page. That is the recommended starting point for teams evaluating LoadStrike in Kubernetes-like environments.
In practice, this is enough for most evaluations: understand the node roles, check the container guidance, and decide whether the published self-hosted cluster model fits the rollout shape your platform team wants to operate.
Platform and performance teams evaluating how the LoadStrike cluster runtime fits into containerized or Kubernetes-adjacent environments.
Kubernetes evaluations usually come down to runtime shape, image strategy, node targeting, and distributed execution. The current docs cover those building blocks through the coordinator-agent model, NATS-backed coordination, and Docker and EKS setup guidance.
LoadStrike gives teams a self-hosted cluster model with explicit coordinator and agent roles, documented container images, and node-targeting support. This page keeps the public cluster guidance connected so a platform team can decide whether the operating model is a match.
These pages cover the cluster and container detail available on the site.
Read the coordinator and agent model first.
Review the cluster roles and communication expectations.
Read the current container and EKS-focused public guidance.
Start with the cluster overview, agents and controller page, and Docker images and EKS page. Those docs cover the coordinator-agent model, transport expectations, and container-focused guidance.
The Docker and EKS guidance is the best starting point when browser dependencies or image contents matter for the workload.
No. The docs focus on the cluster building blocks, Docker images, and EKS-oriented guidance rather than a full Kubernetes platform handbook.
Start with the implementation details that match this page.
Cluster mode lets one LoadStrike run spread across multiple nodes. Use it when a single machine is not enough or when topology matters.
Learn how coordinator and agent nodes split, execute, and merge one clustered LoadStrike run.
This page explains the container build and deployment path for LoadStrike on EKS. Use it when the team wants repeatable images and repeatable cluster runs.
Use these comparison pages if you still need a tool-level decision.
Compare LoadStrike and Apache JMeter across scenario design, protocol coverage, downstream correlation, browser workflows, reporting, and self-hosted operations.
Connect the run output to the observability backend your team already uses.
See how the LoadStrike Grafana Loki sink fits into transaction-aware reporting and public Grafana starter assets.
Read the published category page for clustered execution first.
Connect the deployment model to the broader product framing.
Check plan fit before rollout.
Use the current cluster and container docs to validate the rollout shape, then confirm plan fit and node targeting before you move beyond one host.
