Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

internalOperatorCert appended in weblogic-operator-cm causing issue in OKE addons #4868

Open
gvnc opened this issue May 28, 2024 · 1 comment

Comments

@gvnc
Copy link

gvnc commented May 28, 2024

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 ?

@gvnc 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
@rjeberhard
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants