MTA-4161: Add missing configuration flags to Tackle CR

Signed-off-by: A.Arnold <[email protected]>

Author: anarnold97

docs/topics/mta-7-installing-web-console-on-openshift.adoc

@@ -157,6 +157,38 @@ The most commonly used CR settings are listed in this table:
 |`analyzer_container_requests_memory`
 |`4Gi`
 |Minimum amount of memory the pod needs to run
+
+|`ui_container_limits_cpu`
+|`500m`
+|Maximum number of CPUs the UI pod resource is allowed to use
+
+|`ui_container_limits_memory`
+|`800Mi`
+|Maximum amount of memory the UI pod resource is allowed to use. You can increase this limit if the pod displays `OOMKilled` errors.
+
+|`ui_container_requests_cpu`
+|`100m`
+|Minimum number of CPUs the UI pod resource needs to run
+
+|`ui_container_requests_memory`
+|`350Mi`
+|Minimum amount of memory the UI pod resource needs to run
+
+|`provider_java_container_limits_cpu`
+|`500m`
+|Maximum number of CPUs the Java provider resource is allowed to use
+
+|`provider_java_container_limits_memory`
+|`800Mi`
+|Maximum amount of memory the Java provider resource is allowed to use. You can increase this limit if the pod displays `OOMKilled` errors.
+
+|`provider_java_container_requests_cpu`
+|`100m`
+|Minimum number of CPUs the Java provider resource needs to run
+
+|`provider_java_container_requests_memory`
+|`350Mi`
+|Minimum amount of memory the Java provider resource needs to run
 |====
 
 +