You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose a new feature that provides a unique numerical identifier for each Pod in a Kubernetes Cluster.
In scenarios where the parallelism is set to n, n Jobs are created and deployed to the Cluster.
Each Job, upon instantiation, would get a unique numerical identifier (1, 2, 3, ..., n) stored in the Pod environment variables.
I am willing to contribute to this improvement in the gatling-operator.
Thank you for considering this request.
The text was updated successfully, but these errors were encountered:
andrzejmikolajczakds
changed the title
[Feature Request]: Add pod number as a env into each GatlingRunnerJob pod
[Feature Request]: unique numerical identifier for each Pod in a Kubernetes Cluster
Nov 27, 2024
Summary
I propose a new feature that provides a unique numerical identifier for each Pod in a Kubernetes Cluster.
In scenarios where the parallelism is set to n, n Jobs are created and deployed to the Cluster.
Each Job, upon instantiation, would get a unique numerical identifier (1, 2, 3, ..., n) stored in the Pod environment variables.
I am willing to contribute to this improvement in the gatling-operator.
Thank you for considering this request.
The text was updated successfully, but these errors were encountered: