Remove resource limitation for the operator pod

[iblancasa]

Which problem is this PR solving?

• [Bug]: jaeger-operator pod restarting with OOMKilled with the default memory value #2220

Short description of the changes

• Remove the resource limitation in the operator

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (5244636) 87.51% compared to head (41ede3b) 87.51%.

❗ Current head 41ede3b differs from pull request most recent head 2df4329. Consider uploading reports for the commit 2df4329 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2221   +/-   ##
=======================================
  Coverage   87.51%   87.51%           
=======================================
  Files         100      100           
  Lines        6912     6912           
=======================================
  Hits         6049     6049           
  Misses        658      658           
  Partials      205      205           

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[frzifus]

Iam not sure if that the way how we should solve that. But fine. ^^

[iblancasa]

Iam not sure if that the way how we should solve that. But fine. ^^

@frzifus thanks for accepting the PR :D

From the OpenShift guidelines:

Therefore, cluster components SHOULD NOT be configured with resource limits.

However, cluster components MUST declare resource requests for both CPU and memory.

[frzifus]

From the OpenShift guidelines:

Thx @iblancasa, can you update your branch? I can not, seems you restrict this :)