The `jaeger-operator` pod distributed with "Red Hat OpenShift distributed tracing platform" version 1.42.0-5 is continually restarting with OOMKilled status with the default memory and CPU assigned.
If the memory is increased to 1.5G, then, not more restarts/OOMKilled.
- OCP 4.10
- Red Hat OpenShift distributed tracing platform 1.42.0-5
The Jaeger operator pod restarted with OOMKilled since hitting the default `limits.memory` value of 512Mi making it mostly not usable.
The Jaeger operator pod doesn't restart with OOMKill and the values assigned by default are good enough not to hit the `limits.memory` causing the restart of the pod