Hi all,
did you have any problems with API Connect Operator on OpenShift?
We encounter problems with CrashLoopBackOff API Connect Operator version 3.X of Operator (DPG Operator 1.6 works fine).
We tried installation with CP4I or without and with versions 2.3, 3.0, 3.1 and 3.2 of operator with different OCP 4.10 (installed on VMWare), all the time we have the same problem: Operator pod is stuck on CrashLoopBackOff status. The error log is in attached file.
Operator seems fine: it has green "Installed" status, but there is warning in logs that pod is in crash loop. We do not think it should look like that, but maybe anyone faced this problem...
------------------------------
Bartosz Beling
------------------------------