Modified memory required for Java provider to run in OCP

Author: Prabha Kylasamiyer Sundara Rajan

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

@@ -159,7 +159,7 @@ The most commonly used CR settings are listed in this table:
 |Minimum number of CPUs the pod needs to run
 
 |`analyzer_container_requests_memory`
-|`1Gi`
+|`512Mi`
 |Minimum amount of memory the pod needs to run
 
 |`ui_container_limits_cpu`
@@ -183,15 +183,15 @@ The most commonly used CR settings are listed in this table:
 |Maximum number of CPUs the Java provider resource is allowed to use
 
 |`provider_java_container_limits_memory`
-|`2Gi`
+|`2.5Gi`
 |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`
+|`2.5Gi`
 |Minimum amount of memory the Java provider resource needs to run
 |====
 

docs/topics/mta-requirements-for-java-analyzer.adoc

@@ -6,11 +6,11 @@
 [id="mta-requirements-for-java-analyzer_{context}"]
 = Adding minimum requirements for Java analyzer and discovery
 
-There is a minimum requirement for the Java analyzer, and also the discovery task, which by default is set to 2 GB.
+The minimum requirement for the Java analyzer, and also the discovery task, by default, is set to 2.5 GB.
 
 While this minimum requirement can be lowered to 1.5 GB, it is not recommended.
 
-You can also increase this minimum requirement to more than 2 GB.
+You can also increase this minimum requirement to more than 2.5 GB.
 
 [source, yaml]
 ----
@@ -21,8 +21,8 @@ metadata:
   namespace: openshift-mta
 spec:
   feature_auth_required: 'true'
-  provider_java_container_limits_memory: 2Gi
-  provider_java_container_requests_memory: 2Gi
+  provider_java_container_limits_memory: 2.5Gi
+  provider_java_container_requests_memory: 2.5Gi
 ----
 
 [NOTE]