Description of problem:

If we omit CPU limit in the search CR, operator builds an invalid deployment and throws up an error

Version-Release number of selected component (if applicable):

operator-bundle
sha256:1a20394565bdc61870db1e4443d4d24d0d8eb2d65f3efdffd068cfd389b370ac

How reproducible:

Steps to Reproduce:

1. apply searchv2.yaml

2. check logs of the operator

Actual results:

1.6663425176023073e+09    ERROR    searchoperator    Could not update deployment    {"error": "Deployment.apps \"search-api\" is invalid: spec.template.spec.containers[0].resources.requests: Invalid value: \"50m\": must be less than or equal to cpu limit"}

Expected results:

no error and api deployment updated successfully

Additional info: