xnat-web helm chart contains resource limit settings that can impact deployment

[dean-taylor]

Describe the bug

Warning FailedCreate 67s (x16 over 3m51s) statefulset-controller create Pod xnat-xnat-web-0 in StatefulSet xnat-xnat-web failed error: Pod "xnat-xnat-web-0" is invalid: spec.containers[0].resources.requests: Invalid value: "4": must be less than or equal to cpu limit of 250m

Steps to reproduce

Add resource limits to the nat deployment values.

Expected behavior

Resource limits apply without issue.

XNAT Chart Version

all

Version of Helm

No response

Version of Kubernetes

No response

Additional context

Helm chart best practice is to not apply these values in the template.
There is an argument in Kubernetes that applying a CPU hard limit is an anti pattern that can have unintended resource allocation consequences. This argument stated that this setting should remain unset.