Conversation
|
@shawkins - the Keycloak Benchmark sub-project has some scripts on how to run OpenShift on AWS. It has its downsides: it takes ~45 minutes to spin up a cluster. With the new architecture of OpenShift on AWS this might be down to 15 minutes, and there could be options to not spin up a cluster for everything. Let's talk. |
|
I think we should be able to hook up to OpenShift CI / clusterbot in some way. |
|
In any case, QE is testing the Operator with OCP internally. I wonder why it wasn't caught before. @miquelsi |
It takes running a failing scenario - where the statefulset is failing to rollout to trigger this logic. |
|
QE is AFAIK running the full remote testsuite on OCP nightly. @miquelsi Is that correct? |
|
@shawkins BTW, we should backport this to 22. Can you please look into it? |
Unfortunately the minikube remote tests still pass even without this permission - I wasn't aware of this difference openshift handling.
I know fabric8 is still stuck at integration testing with openshift 3.11 - is there any desire around pushing to have something 4.x based runnable in a github action?
Closes #21814