Merge pull request #80 from anarnold97/MTA-4161-Configuration-flags-Tackle-CR

MTA-4161: Add missing configuration flags to Tackle CR

Author: anarnold97

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

@@ -95,11 +95,11 @@ The most commonly used CR settings are listed in this table:
 |Storage class used for the cache volume; ignored when `rwx_supported=false`
 
 |`feature_auth_required`
-|`True`
+|`true`
 |Flag to indicate whether keycloak authorization is required (single user/"`noauth`")
 
 |`feature_isolate_namespace`
-|`True`
+|`true`
 |Flag to indicate whether namespace isolation using network policies is enabled
 
 |`hub_database_volume_size`
@@ -118,6 +118,10 @@ The most commonly used CR settings are listed in this table:
 |`1Gi`
 |Size requested for the Keycloak database volume
 
+|`keycloak_sso_req_passwd_update`
+|`true`
+|If the flag is set to `true`, users are required to update their password after their first login.
+
 |`pathfinder_database_data_volume_size`
 |`1Gi`
 |Size requested for the Pathfinder database volume
@@ -131,7 +135,7 @@ The most commonly used CR settings are listed in this table:
 |Storage class requested for the Tackle RWX volumes; deprecated in {ProductShortName} 6.0.1
 
 |`rwx_supported`
-|`True`
+|`true`
 |Flag to indicate whether the cluster storage supports RWX mode
 
 |`rwo_storage_class`
@@ -157,6 +161,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`
+|`1`
+|Maximum number of CPUs the Java provider resource is allowed to use
+
+|`provider_java_container_limits_memory`
+|`2Gi`
+|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`
+|`1`
+|Minimum number of CPUs the Java provider resource needs to run
+
+|`provider_java_container_requests_memory`
+|`2Gi`
+|Minimum amount of memory the Java provider resource needs to run
 |====
 
 +