-
Bug
-
Resolution: Done
-
Blocker
-
7.12.0.GA, 7.12.1.GA
-
None
-
OCP 4.9
BA Operator 7.12.1
-
False
-
-
False
-
-
-
-
-
-
CR2
-
- Deploy BA Operator on OCP 4.9
- Run simple KieApp (e.g. rhpam-trial)
- Check BA Operator pod, that logs does not contain failing checks
-
When Operator is deployed to namespace and new KieApp is created, then BA Operator pod's log is flooded by failing checks that objects and/or resources are not equal. Looks like this is caused by internal traffic policy in object or resource set to `"internalTrafficPolicy": "Cluster"` (probably by default in OCP 4.9) and not expected configuration like this by Operator.
See part of log for deployed and requested objects:
{
"logger": "comparator",
"msg": "Objects are not equal",
"deployed": {
"ports": [
{
"name": "http",
"port": 8080,
"targetPort": 8080
},
{
"name": "https",
"port": 8443,
"targetPort": 8443
}
],
"selector": {
"deploymentConfig": "rhpam-trial-rhpamcentr"
},
"internalTrafficPolicy": "Cluster"
},
"requested": {
"ports": [
{
"name": "http",
"port": 8080,
"targetPort": 8080
},
{
"name": "https",
"port": 8443,
"targetPort": 8443
}
],
"selector": {
"deploymentConfig": "rhpam-trial-rhpamcentr"
}
}
}
I was not able to detect issue like this on OCP 4.8 or 4.6
