kane8n

@andrzejmikolajczakds Thank you for creating the issue! This is similar to the following PullRequest. - https://github.com/st-tech/gatling-operator/pull/120 The current implementation works with gatling 3.10, but not with 3.11 as you mentioned....

@andrzejmikolajczakds Please submit a PullRequest for document updates and we will review it!

Thanks for the PullRequest! It seems to work fine with gatling 3.11. However, there seems to be a backward compatibility issue, so please let me check.

@annappropriate Sorry for the very long wait. We will implement the following for gatling 3.11 support to maintain backward compatibility. Please test if it works with this PullRequest ahead of...

@annappropriate Sorry for the late reply. I think it is because you still have an old version of controller-gen in `/workspaces/gatling-operator/bin/`. The tools under `/workspaces/gatling-operator/bin/` are installed with `go-install-tool` defined...

@kkulak Thank you for your detailed research! I did confirm that reports are only generated from a single log file in 3.12. - ref: https://github.com/gatling/gatling/commit/2fb207dabf97a17e87d705991ca2145b6bd2b85a First of all, support for...

@andrzejmikolajczakds Thank you for your suggestions! Could you inform me of explain in more detail the benefits of implementing this?

@andrzejmikolajczakds Sorry for the late reply. I understand the situation! If you can get me a PR, I will review it for you!

@pgouband Thanks for your reply! It seems that awx-operator is running on an AWS EKS cluster and for some reason was experiencing unstable communication with `product.apis.f5.com`. It is difficult to...

As a side note, when this error occurs, the ansible job fails, but the BIG-IP operation (in this case, unloading the server from the pool) itself succeeds.