add jcasc auto reload sidecar resources

[charliehanaceksonos]

What does this PR do?

This PR updates the values summary documentation to include a reference to how to set resource requests and limits for the configAutoReload. Exposing the resource limits and requests for the sidecar allows them to be set to the same value, which allows the whole Pod to be granted a "Guaranteed" QoS class. The helmchart already supports this, though it wasn't reflected in the docs already.

If you modified files in the ./charts/jenkins/ directory, please also include the following:

Submitter checklist

Preview Give feedback

1. I bumped the "version" key in ./charts/jenkins/Chart.yml.
2. I added a new changelog entry to ./charts/jenkins/CHANGELOG.md.
3. I followed the technical requirements.

Special notes for your reviewer

[timja]

unsure if this is required, from what I understand it's VALUES_SUMMARY.md not VALUES.md

this means some will be omitted especially less interesting ones, all values should be in values.yaml, and commented out if not set, see

helm-charts/charts/jenkins/values.yaml

Lines 371 to 377 in f60c959

	resources: {}
	# limits:
	# cpu: 100m
	# memory: 100Mi
	# requests:
	# cpu: 50m
	# memory: 50Mi

[charliehanaceksonos]

I was only trying to make the documentation consistent, since the other containers specified in values.yaml had references to their associated resources in VALUES_SUMMARY.md. I'll close the PR if you're not going to accept someone offering to improve the docs.

[charliehanaceksonos]

Would you accept a change adding matching resource requests and limits for the auto config reload container?

[timja]

I was only trying to make the documentation consistent, since the other containers specified in values.yaml had references to their associated resources in VALUES_SUMMARY.md. I'll close the PR if you're not going to accept someone offering to improve the docs.

I see, happy to take the PR, would you be able to resolve the conflicts please?