Adds request and limit parameters with more reasonable values based on actual usage across several clusters. This also removes the extraneous/unused resources section under strategy in many of the templates which were misleading people into add/updating resource values there in addition to the correct ones under the spec template containers. I think the reason they weren't flagged as incorrect by OpenShift is the support for deployment strategy custom which could include user-defined properties of unknown name.
Why
This will allow self-managed customers as well as the NOC for hosted customers to adjust the values of specific components based on their actual usage rather than forcing every install to hard-coded worst-case scenario values.
How
Required parameters added to all versions of component templates with default values set so that they will be available going forward without any additional configuration for most installs.
Verification Steps
These template versions are backwards compatible with any method of installation by referencing the folder containing them.
Checklist:
[x] Code has been tested locally by PR requester
[ ] Changes have been successfully verified by another team member
Jira link(s)
https://issues.jboss.org/browse/RHMAP-21570
What
Adds request and limit parameters with more reasonable values based on actual usage across several clusters. This also removes the extraneous/unused resources section under strategy in many of the templates which were misleading people into add/updating resource values there in addition to the correct ones under the spec template containers. I think the reason they weren't flagged as incorrect by OpenShift is the support for deployment strategy custom which could include user-defined properties of unknown name.
Why
This will allow self-managed customers as well as the NOC for hosted customers to adjust the values of specific components based on their actual usage rather than forcing every install to hard-coded worst-case scenario values.
How
Required parameters added to all versions of component templates with default values set so that they will be available going forward without any additional configuration for most installs.
Verification Steps
These template versions are backwards compatible with any method of installation by referencing the folder containing them.
Checklist: