Post-installation steps

Providing configuration files during probe pod initialization

The command below shows how to add custom probe files into the PV from local directory during probe pod initialization. You only perform this step once for a new PVC. The probe will not start until all files are successfully transferred.

oc rsync  ./ <probe pod>:/home/netcool/etc/custom_probe_files -c custom-probefiles-wait --strategy=tar

Updating configuration files in the persistent volume

The command below shows how to update custom probe files stored in PV from local directory when probe pod is running. The local directory contains the updated probe files.

oc rsync  ./ <probe pod>:/home/netcool/etc/custom_probe_files --strategy=tar

You must run the commands below to scale down the number of replicas to zero and scale up to the desired replica count to ensure that the probe pods reload with the updated configuration file and rules files from the PV.

oc scale deployment <probe deployment> --replicas=0

oc scale deployment <probe deployment> --replicas=<desired replica count>

Updating probe rules files

If you are only updating the custom rules files in the persistent volume, run the command below to trigger the probe to reload the updated rules files. You must run this command on every pod if there are more than one probe pod replicas so that all pods run with the same rules.

oc exec <probe pod>  \
-n <namespace>   -it \
-- curl -X PUT http://<probe pod>:8080/probe/common/reloadrules \
-H 'Content-type:application/json' \
-d  '{"reloadrulesflag":1}'