Increase CPU limit to 1 to support heavier template processing

[Smiley73]

Description

Complex helm charts take forever to process. This change allows the pod to take up to 1 CPU (limit), but leaves the request at 200m.

Type of change

• Bug fix (non-breaking change which fixes an issue)

Checklist

• Unit tests and e2e tests updated
• Documentation updated

[sanbornick]

lgtm

[codecov]

Codecov Report

Merging #361 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #361   +/-   ##
=======================================
  Coverage   25.00%   25.00%           
=======================================
  Files           6        6           
  Lines         536      536           
=======================================
  Hits          134      134           
  Misses        373      373           
  Partials       29       29           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9d36e3e...717618e. Read the comment docs.

[vinny-sabatini]

I'm ok with this, but something to keep in mind is the job request and limits are currently configurable without making the change to Eunomia directly.
Ref: https://github.com/KohlsTechnology/eunomia#job-templates

I believe there was talk of possibly making the requests/limits available in the CRD whenever we re-visit the definition, but the v1alpha2 discussion has been on hold at this point.

[Smiley73]

Yeap. In v1alpha2 we want to actually move the resource setting into the CR, to be more flexible. Changing the template is a cluster-wide thing..