Creating or Updating the YAML File for the Loader Utility

The Loader utility YAML file is present in the CNC NF Data Collector tar package. You can either update the existing YAML file or create a new YAML file with the following parameters which can be configured. Oracle recommends to consider the existing file that is available with the tar package and update its parameters.

For information about parameter descriptions, refer to loader-custom-values.yaml Parameter Description.

1. Update the global.image.repository parameter by providing the name of the docker registry where the cnc-nfdata-collector image is present.
2. Update the global.slaveNodeName parameter by providing the name of the kubernetes worker node that can load the collected data from this utility.
   To obtain the name of the worker node or slave node, execute the kubectl get nodes command. The names of all the master and worker nodes of the kubernetes cluster are displayed in the Name column. You can provide the name of one of the worker nodes from the generated output.
3. Update the global.inputPath parameter by providing the path of the exported-data directory present on the kubernetes cluster worker node in global.slaveNodeName.
   1. Ensure that the exported data is accessible by non-root users for read or write operation.
4. Update the global.capacityStorage parameter by specifying the estimated amount of space required to occupy the collected data, for example, 2Gi, 200Mi, and so on.
   The value specified here is the space provided to kubernetes persistence volume that is mounted with this utility to enable collected data accessible to loader job.
5. Update the global.elasticSearchURL parameter by specifying the URL for Elastic search.
   FQDN of Elastic search can also be provided. If Elastic search requires authentication, it can be provided in the URL as http://<user-name>:<password>@<elastic-search-url>:<elastic-search-port>.

   To find the FQDN, execute kubectl get svc –n <namespace> and retrieve the Elastic search service name. After that, FQDN can be constructed as http://<elastic-search-service-name>.<namespace>:<port>. The default Elastic search port is 9200. The administrator of the cluster must be asked for the user name and password of Elastic search if required.

6. Update the global.victoriaMetricsURL parameter by specifying the URL for the Victoria Metrics.
   FQDN of Victoria Metrics can also be provided.