You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
internalOperatorCert fields is not part of helm charts and not created initially in configmap weblogic-operator-cm, but generated and appended to configmap when pods start to run.
This is causing issues in OKE addons framework because OKE periodically runs checks on addon k8s resources to detect any discrepancies between the initial definitions and the actual ones and runs a reconciliation process.
In this case, internalOperatorCert is found as a diff and removed from config map if WKO is installed via addons.
Could you work on a solution to save internalOperatorCert in a different way ?
The text was updated successfully, but these errors were encountered:
gvnc
changed the title
internalOperatorCert inserted in weblogic-operator-cm causing issue
internalOperatorCert appended in weblogic-operator-cm causing issue in OKE addons
May 28, 2024
We acknowledge that the behavior for this CM entry is incompatible with the behavior of the OKE add-on framework. The good news is that this field is only used for the REST endpoint of the operator, which is deprecated. This is a separate endpoint from the REST endpoint provided by the webhook that is for the schema conversion and validating webhooks.
Likely, this issue will simply be solved by our removing the operator's REST endpoint.
internalOperatorCert fields is not part of helm charts and not created initially in configmap weblogic-operator-cm, but generated and appended to configmap when pods start to run.
This is causing issues in OKE addons framework because OKE periodically runs checks on addon k8s resources to detect any discrepancies between the initial definitions and the actual ones and runs a reconciliation process.
In this case, internalOperatorCert is found as a diff and removed from config map if WKO is installed via addons.
Could you work on a solution to save internalOperatorCert in a different way ?
The text was updated successfully, but these errors were encountered: