19.3 Setting up of Remote Loader Service on Azure Kubernetes Service

Perform the following steps to setup Remote Loader service on Azure Kubernetes Service:

Create Persistent Volume (PV) and Persistent Volume Claim(PVC) for persisting the Remote Loader data.
Inside the PV, create a directory rdxml.
In the rdxml directory, create the driverconf directory.
In the rdxml directory, create the keystore directory.
Copy all the required keystore files and certificates to the keystore directory.
In the rdxml directory, create a new .txt file. For example, StartupRL.txt.
In the StartupRL.txt file, specify the required content in the following format:

<Remote Loader configuration file> -sp <driver password> <Remote Loader password>

For example:

config8000.txt -sp dirxml dirxml

Alternatively, you can also specify the entries in the following format:

<Remote Loader configuration file> -ksp <keystore password> -kp <key password>

For example:

config8000.txt -ksp dirxml -kp dirxml

From the container tarball, copy helm-charts/rl-values.yaml and update the following fields in the file:

Table 19-3

Section	Fields	Description
Registry credentials for Remote Loader docker images	registry	Specify the Azure Container Registry Server Name.
Registry credentials for Remote Loader docker images	name	Specify the name of the Kubernetes secret which contains the login credentials of the registry.
Data Persistence	Shared Persistent Storage existingClaim dynamicClaim: storageClassName storageSize	If you want to use an existing Persistent Volume Claim (PVC), enter the name of the existing claim. Else, for dynamic provisioning of PVC, specify the storage class name and the storage size.
Driver Startup File	driverStartupFileName	Specify Name of the driver startup file. For example, StartupRL.txt
Remote Loader Service	ports	Specify the list of ports Remote Loader service listening on.
Resource Requests and Limits	Resource requests cpu memory	Specify the cpu and memory values of resource requests. for more details refer Resource Management for Pods and Containers
Resource Requests and Limits	Limits cpu memory	Specify the cpu and memory values of limits. for more details refer Resource Management for Pods and Containers

From the container tarball, copy helm-charts/ remote-loader-1.3.0.tgz and run the following helm command to install remote loader:
```
helm install remote-loader helm_charts/remote-loader-1.3.0.tgz --namespace idm -f rl-values.yaml
```
(Optional) If you want to install multiple remote loader, Copy helm-charts/ remote-loader-1.3.0.tgz from the container tarball, and run the following helm command:
```
helm install <remote-loader-n> helm_charts/remote-loader-1.3.0.tgz --namespace idm -f rl-values.yaml
```
In remote-loader-n, where n is nth remote loader getting installed.

For example:

If you are installing two remote loaders, Then the command to install second remote loader will be

helm install remote-loader-2 helm_charts/remote-loader-1.3.0.tgz --namespace idm -f rl-values.yaml