fix(operator): adapt resource requests and limits

[bacherfl]

Closes #832
Signed-off-by: Florian Bacher [email protected]

[codecov]

Codecov Report

Merging #835 (59666b5) into main (0edd9c1) will increase coverage by 0.14%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #835      +/-   ##
==========================================
+ Coverage   58.52%   58.67%   +0.14%     
==========================================
  Files          97       97              
  Lines        7552     7552              
==========================================
+ Hits         4420     4431      +11     
+ Misses       2939     2932       -7     
+ Partials      193      189       -4     

Impacted Files	Coverage Δ
...lers/lifecycle/keptnworkloadinstance/controller.go	82.51% <0.00%> (+0.89%)	⬆️
...ator/controllers/lifecycle/keptntask/controller.go	58.24% <0.00%> (+3.29%)	⬆️
...ptnworkloadinstance/reconcile_prepostdeployment.go	90.90% <0.00%> (+9.09%)	⬆️
...ptnworkloadinstance/reconcile_prepostevaluation.go	90.90% <0.00%> (+9.09%)	⬆️

Flag	Coverage Δ
component-tests	41.92% <ø> (+0.40%)	⬆️
keptn-lifecycle-operator	54.67% <ø> (ø)
klt-cert-manager	67.50% <ø> (ø)
scheduler	21.17% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[mowies]

why don't you put the resource settings directly into the manifests instead of using the kustomize patch files?

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[bacherfl]

why don't you put the resource settings directly into the manifests instead of using the kustomize patch files?

no particular reason; i saw that those were also set in the patch for the rbac-proxy container and did it the same way for the manager - but i agree that it makes more sense to set them in the manifests directly.