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
Since enabling webhooks within Openshift within ECK, it was found that Openshift 4.6 and below have issues where they mount the Certificates in a location that doesn't align with the Operator SDK, and as such, the operator goes into a CrashLoopBackoff.
We will need to find a solution for supporting these older versions of openshift and the webhook, either with a code fix, or simply disabling the webhook within openshift.
Known workarounds as of now:
remove --enable-webhook flag from the list of args in the elastic-operator container via the yaml definition for the operator within the Openshift UI. (Operators -> Installed Operators -> Elasticsearch (ECK) Operator -> Operator details -> YAML)
Upgrade Openshift to version 4.7
The text was updated successfully, but these errors were encountered:
Since enabling webhooks within Openshift within ECK, it was found that Openshift 4.6 and below have issues where they mount the Certificates in a location that doesn't align with the Operator SDK, and as such, the operator goes into a
CrashLoopBackoff
.Bug fix reference in 4.7 release notes:
https://docs.openshift.com/container-platform/4.7/release_notes/ocp-4-7-release-notes.html#ocp-4-7-bug-fixes
Bugzilla reference:
https://bugzilla.redhat.com/show_bug.cgi?id=1879248
We will need to find a solution for supporting these older versions of openshift and the webhook, either with a code fix, or simply disabling the webhook within openshift.
Known workarounds as of now:
--enable-webhook
flag from the list of args in theelastic-operator
container via the yaml definition for the operator within the Openshift UI. (Operators -> Installed Operators -> Elasticsearch (ECK) Operator -> Operator details -> YAML)The text was updated successfully, but these errors were encountered: