Nitish Malhotra

@waghanza @fenollp @tsenart Would you prefer the REST server to use the library or use `exec` and invoke the `vegeta` CLI ? I cooked up a simple `swagger` spec, and...

@tsenart I have started working on this. IMO it might be better suited for a separate repository, that uses the `vegeta` library. I am creating a `Swagger` spec for this,...

> > IMO it might be better suited for a separate repository, that uses the vegeta library. > > To make it clear to everyone in the future about this...

> Creating the server package, and wrappers that utilize the vegeta library, as a separate entity makes it easier to maintain the special handing logic of the API request/response Can...

Cool. Let me see if I can figure out how to get `go-swagger` to generate a more flat directory structure.

I have created a project that implements the REST API for vegeta - https://github.com/nitishm/vegeta-server Personally it was easier to spin this off into its own project rather than integrate it...

How do you envision using operators ? What would the CRD specify ? It would be nice to start with a simple master/worker model, deploying workers as a daemonset across...

My thought is to use a kubernetes operator (acting as the master, driven by `CRD`s and a worker `replicationset` for horizontal scalability (via multiple replica pods) model. The operator will...

I agree with jobs as well. My thought process was driven by this article on using locust on GKE https://cloud.google.com/solutions/distributed-load-testing-using-kubernetes.

@kaidotdev How do you scale the attacks ? Or is a single attack carried out by a single job pod ?