<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>System Requirements on</title><link>https://docs.protegrity.com/protectors/10.1/docs/apjava_container/iap_java_system_requirements/</link><description>Recent content in System Requirements on</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.protegrity.com/protectors/10.1/docs/apjava_container/iap_java_system_requirements/index.xml" rel="self" type="application/rss+xml"/><item><title>Software Requirements</title><link>https://docs.protegrity.com/protectors/10.1/docs/apjava_container/iap_java_system_requirements/iap_java_verifying_the_prereq_/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/protectors/10.1/docs/apjava_container/iap_java_system_requirements/iap_java_verifying_the_prereq_/</guid><description>&lt;p>Ensure that the following prerequisites are met for deploying the Application Protector Java Container package &lt;strong>ApplicationProtector_RHUBI-9-64_x86-64_Generic.K8S.JRE-&amp;lt;JRE_Version&amp;gt;_&amp;lt;Version&amp;gt;.tgz&lt;/strong>.&lt;/p>
&lt;h3 id="esa-prerequisites">ESA prerequisites&lt;/h3>
&lt;ul>
&lt;li>
&lt;p>Policy – Ensure that you have defined the security policy in the ESA.
For more information about defining a security policy, refer to the section &lt;a href="https://docs.protegrity.com/10.1/docs/pmg/pmg_creating_deploying_policies/">Policy Management&lt;/a>.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Datastore - Attach the policy to the default datastore in the ESA or to a range of allowed servers that are added to a datastore.&lt;/p>
&lt;p>The IP address range of the allowed servers must be the same as that of the nodes in the Kubernetes cluster where the Application Protector Java Containers are deployed.&lt;/p></description></item><item><title>Hardware Requirements</title><link>https://docs.protegrity.com/protectors/10.1/docs/apjava_container/iap_java_system_requirements/iap_java_hardware_requirements/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/protectors/10.1/docs/apjava_container/iap_java_system_requirements/iap_java_hardware_requirements/</guid><description>&lt;p>The following table lists the minimum hardware configuration for each pod where the Application Protector Java Container is deployed.&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Hardware Components&lt;/th>
 &lt;th>Configuration&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>CPU&lt;/td>
 &lt;td>Depends on the application.&lt;br>By default, the value is set to:&lt;ul>&lt;li>1000 millicores or 1 CPU for the Application Protector Java Container.&lt;li>200 millicores or 0.2 CPU for the Policy Loader container.&lt;li>500 millicores or 0.5 CPU for the RPProxy container.&lt;li>300 millicores or 0.3 CPU for the Log Forwarder container.&lt;li>500 millicores or 0.5 CPU for the KMS-Proxy container.&lt;/ul>&lt;br>For more information about the CPU requirements for each container, refer to the &lt;em>values.yaml&lt;/em> file for the corresponding container.&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>RAM&lt;/td>
 &lt;td>Depends on the workload.&lt;br>By default, the value is set to:&lt;ul>&lt;li>3000 MB for the Application Protector Java Container.&lt;li>512 MB for the Policy Loader container.&lt;li>512 MB for the RPProxy container.&lt;li>328 MB for the Log Forwarder container.&lt;li>512 MB for the KMS-Proxy container.&lt;/ul>&lt;br>For more information about the memory requirements for each container, refer to the &lt;em>values.yaml&lt;/em> file for the corresponding container.&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>The instance type used for the cluster node is t3.2xlarge. The minimum CPU requirement for the node is 8 vCPU and the minimum memory capacity is 32 GiB.&lt;/p></description></item></channel></rss>