<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>REST Container on</title><link>https://docs.protegrity.com/protectors/10.0/docs/rest_container/</link><description>Recent content in REST Container on</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.protegrity.com/protectors/10.0/docs/rest_container/index.xml" rel="self" type="application/rss+xml"/><item><title>Using Samples</title><link>https://docs.protegrity.com/protectors/10.0/docs/rest_container/iap_rest_using_samples/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/protectors/10.0/docs/rest_container/iap_rest_using_samples/</guid><description>&lt;p>Protegrity delivers a sample application as part of the REST Container installation package. The sample application consists of the following items:&lt;ul>&lt;li>Policy package.&lt;li>Sample Postman collection (to test AP-REST Container Pods serving deployed IMP).&lt;li>Autoscaling script (to push more load to the Kubernetes cluster to force autoscaling of the AP-REST Container Pods).&lt;/ul>&lt;/p>
&lt;p>Run this sample application end-to-end, as a sanity test. This will enable them to confirm that the installation was completed accurately. In this section are details on the exact steps a customer must follow to run the sample application end-to-end. Those details explain usage of the components included in &lt;strong>REST-Samples_Linux-ALL-ALL_x86-64_&amp;lt;AP-REST_version&amp;gt;.tgz&lt;/strong> archive.&lt;/p></description></item><item><title>Running the Autoscaling Script</title><link>https://docs.protegrity.com/protectors/10.0/docs/rest_container/iap_rest_using_run_autoscaling_script/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/protectors/10.0/docs/rest_container/iap_rest_using_run_autoscaling_script/</guid><description>&lt;p>The Autoscaling script is used to issue continuous requests on the AP-REST containers. When the number of REST requests hitting the container are increased, with Horizontal Pod Autoscaling, Kubernetes automatically scales the number of pods based on the CPU utilization observed.&lt;/p>
&lt;p>The user can run the autoscaling script from any Linux node, which can connect the external IP for the deployment.&lt;/p>
&lt;p>&lt;strong>Usage&lt;/strong>&lt;/p>
&lt;p>&lt;code>./Sample_App_autoscale.sh &amp;lt;Ingress address&amp;gt; &amp;lt;CA certificate path&amp;gt; &amp;lt;Client certificate path&amp;gt; &amp;lt;Client key path&amp;gt; &amp;lt;version_endpoint&amp;gt;&lt;/code>&lt;/p></description></item><item><title>Using Dockerfiles to Build Custom Images</title><link>https://docs.protegrity.com/protectors/10.0/docs/rest_container/iap_rest_using_dockerfiles_for_custom_images/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/protectors/10.0/docs/rest_container/iap_rest_using_dockerfiles_for_custom_images/</guid><description>&lt;p>Protegrity base images use the default RHEL Universal Base Image. Using Dockerfiles, you can use a base image of your choice.&lt;/p>
&lt;p>To create custom image:&lt;/p>
&lt;ol>
&lt;li>
&lt;p>Download the installation package.&lt;/p>
&lt;p>For more information about downloading the installation package, refer to the section &lt;a href="https://docs.protegrity.com/protectors/10.0/docs/rest_container/iap_preparing_environment/iap_rest_extracting_package/">Extracting the Installation Package&lt;/a>.&lt;/p>
&lt;p>&lt;strong>Important:&lt;/strong> The dependency packages required for building the Docker images are specified in the &lt;strong>HOW-TO-BUILD&lt;/strong> file, which is a part of the installation package. You must ensure that these dependency packages can be downloaded either from the Internet or from your internal repository.&lt;/p></description></item><item><title>Appendix - Deploying the Helm Charts by Using the Set Argument</title><link>https://docs.protegrity.com/protectors/10.0/docs/rest_container/iap_rest_using_set_arguments/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/protectors/10.0/docs/rest_container/iap_rest_using_set_arguments/</guid><description>&lt;p>To deploy Helm charts using the &lt;em>set&lt;/em> argument:&lt;/p>
&lt;ol>
&lt;li>Navigate to the directory where you have stored the &lt;em>values.yaml&lt;/em> file for deploying the corresponding Helm chart.&lt;/li>
&lt;li>Deploy the Helm chart using the following command.&lt;/li>
&lt;/ol>
&lt;div class="highlight">&lt;pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-fallback" data-lang="fallback">&lt;span style="display:flex;">&lt;span> helm install &amp;lt;name for this helm deployment&amp;gt; &amp;lt;Location of the directory that contains the Helm chart&amp;gt; -n &amp;lt;Namespace&amp;gt;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> --set &amp;lt;tag 1&amp;gt;=&amp;#34;Value 1&amp;#34;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> --set &amp;lt;tag 2&amp;gt;=&amp;#34;Value 2&amp;#34;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> --set &amp;lt;tag 3&amp;gt;=&amp;#34;Value 3&amp;#34;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> --set &amp;lt;tag 4&amp;gt;=&amp;#34;Value 4&amp;#34;
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;strong>For example&lt;/strong>:&lt;/p></description></item></channel></rss>