search

st-tech / gatling-operator

Automating distributed Gatling load testing using Kubernetes operator
MIT License
70 stars 19 forks source link

Modify Gatling Runner Pod’s Multi-Containers Structure #64

Closed yokawasa closed 1 year ago

yokawasa commented 1 year ago

Description

Currently, as described in architecture diagram (see Gatling Operator Architecture and Design), gatling-waiter and gatling-runner container run as init containers and gatling-result-transferer as a main container in the case of generating an aggregated Gatling result report while gatling-runner runs as a main container in the case of not generating the report.

My proposal in the issue is that gatling-waiter runs as an init container and both gatling-runner and gatling-result-transferer should run as main containers in a Gatling Runner Pod. It's generally expected behavior that gatling-runner runs as a main container in Gatling Runner Pod as it's main workload.

yokawasa commented 1 year ago

self assigned to @yokawasa

yokawasa commented 1 year ago

closing the issue as the relevant PR has been merged https://github.com/st-tech/gatling-operator/pull/65