Feature Request: Ability to configure limits and requests of CPU/Memory on PolicyServer CRD

[brunorene]

Is your feature request related to a problem?

Yes at the moment we need to create a LimitRange resource to limit memory for the policy server deployment.

Solution you'd like

The PolicyServer CRD would have a block to configure limits and requests for CPU and memory for the policy server deployment and also be able to configure it through kubewarden-defaults Helm Chart.

Alternatives you've considered

At the moment we are using LimitRange but it applies to all the namespace so it is not a very good solution.

Anything else?

Not really thanks

[viccuad]

Relates to #564.

[flavio]

Admission Criteria

• The PolicyServer CRD has two new attributes: limits and requests. Both are optional and have type ResourceList. See the ResourceRequirements definition for details:
  feat: add limits and requests to PolicyServer #708

• These attributes are propageted by the kubewarden-controller into the Deployment definition of the Policy Server. More specifically, they are attributes set inside of the container that runs the Policy Server process:
  feat: add limits and requests to PolicyServer #708

• The helm charts are updated to allow tuning of these new attributes: feat: add limits and requests to PolicyServer helm-charts#417

• The CRD documentation is updated to reflect this change: docs: update generated PolicyServer CRD docs with limits and requests docs#389

• The project documentation mentions this new attribute Add docs for limits/requests, affinity, reword PDB docs#393

• Expose anti-affinity, PDB, limits and requests in questions.yaml helm-charts#418

[viccuad]

Skipping exposing this new features through Rancher UI, see kubewarden/helm-charts#418.

With that, this is done, will get shipped on the next release.