Kamesh Akella

It would be great to get support for Openshift clusters and have testkube run as non-root, love to benefit from the plugin @vsukhin

@VfanLee thanks for providing the docker assets to deploy, I was able to successfully bring up the containers but after selecting the username and password for mysql I am stuck...

@VfanLee thanks I think giving an actual server ip worked instead of the localhost I was trying. I am able to complete the setup now on my M1 Mac and...

@martin-kanis I understand the value in running Keycloak testsuite against a crossdc setup, however that would be a case to be made in `Keycloak` and `testsuite` is probably the right...

@ahus1 sure thing, let me see if I can get in a task to re-arm the route53 health check after we do the restart as needed, it would also mean...

@ahus1 https://github.com/kami619/keycloak-benchmark/actions/runs/8973649052/job/24644308418#step:27:111 this failed again for same reason, even though both the sites are working and route53 health checks are reporting healthy. [It succeeded a prior attempt](https://github.com/kami619/keycloak-benchmark/actions/runs/8973649052/job/24644308418#step:23:76), so not sure...

Do we have an Active/Active functional test available in a branch somewhere ? @pruivo, @mhajas ?

@ahus1 For this particular item, I think we already mentioned it under the `Running in production` guide for a [basic Keycloak deployment](https://www.keycloak.org/keycloak-benchmark/kubernetes-guide/latest/running/keycloak-deployment#optional-disable-sticky-sessions). Can we tick this off in this case...

@pruivo I believe the CPU cycles are spent on creating users in the `Creating Realms` section right ? What is the impact on CPU if we purely create users similar...

We seem to get this WARN message when we are using the default hashing iteration to create users, seems to be logged for each user created. We should tune this...