OCPBUGS-27961 Procedure for configuring Whereabouts IP reconciler schedule

making edits to reflect my cluster test

Author: Kevin Quinn

modules/nw-multus-ipam-object.adoc

@@ -310,4 +310,72 @@ pod/whereabouts-reconciler-p4sxw 1/1 Running 0 6s
 pod/whereabouts-reconciler-rvfdv 1/1 Running 0 6s
 pod/whereabouts-reconciler-svzw9 1/1 Running 0 6s
 daemonset.apps/whereabouts-reconciler 6 6 6 6 6 kubernetes.io/os=linux 6s
+----
+
+[id="nw-multus-configuring-whereabouts-ip-reconciler-schedule_{context}"]
+== Configuring the Whereabouts IP reconciler schedule
+
+The Whereabouts IPAM CNI plugin runs the IP reconciler daily to clean up any stranded IP allocations that may result in exhausting IPs and therefore prevent new Pods from getting an IP allocated to them.
+
+The following procedure shows how to change the frequency at which the IP reconciler runs. 
+
+.Prerequisites
+* You installed the OpenShift CLI (`oc`).
+* You have access to the cluster as a user with the `cluster-admin` role.
+
+.Procedure
+
+. Run the following command to create a `ConfigMap` named `whereabouts-config` in the `openshift-multus` namespace with a specific cron expression for the IP reconciler:
++
+[source,terminal]
+----
+$ oc create configmap whereabouts-config -n openshift-multus --from-literal=reconciler_cron_expression="*/15 * * * *"
+----
++
+This cron expression indicates the IP reconciler runs every 15 minutes. Adjust the expression based on your specific requirements.
+
+. Retrieve information about resources related to the `whereabouts-reconciler` within the `openshift-multus` namespace by running the following command:
++
+[source,terminal]
+----
+$ oc get all -n openshift-multus | grep whereabouts-reconciler
+----
++
+.Example output
++
+[source,terminal]
+----
+pod/whereabouts-reconciler-2p7hw                   1/1     Running   0             4m14s
+pod/whereabouts-reconciler-76jk7                   1/1     Running   0             4m14s
+pod/whereabouts-reconciler-94zw6                   1/1     Running   0             4m14s
+pod/whereabouts-reconciler-mfh68                   1/1     Running   0             4m14s
+pod/whereabouts-reconciler-pgshz                   1/1     Running   0             4m14s
+pod/whereabouts-reconciler-xn5xz                   1/1     Running   0             4m14s
+daemonset.apps/whereabouts-reconciler          6         6         6       6            6           kubernetes.io/os=linux   4m16s
+----
+
+. Run the following command to verify that the `whereabouts-reconciler` runs the IP reconciler with the configured interval:
++
+[source,terminal]
+----
+$ oc -n openshift-multus logs whereabouts-reconciler-2p7hw
+----
++
+.Example output
+
+[source,terminal]
+----
+2024-02-02T16:33:54Z [debug] event not relevant: "/cron-schedule/..2024_02_02_16_33_54.1375928161": CREATE
+2024-02-02T16:33:54Z [debug] event not relevant: "/cron-schedule/..2024_02_02_16_33_54.1375928161": CHMOD
+2024-02-02T16:33:54Z [debug] event not relevant: "/cron-schedule/..data_tmp": RENAME
+2024-02-02T16:33:54Z [verbose] using expression: */15 * * * *
+2024-02-02T16:33:54Z [verbose] configuration updated to file "/cron-schedule/..data". New cron expression: */15 * * * *
+2024-02-02T16:33:54Z [verbose] successfully updated CRON configuration id "00c2d1c9-631d-403f-bb86-73ad104a6817" - new cron expression: */15 * * * *
+2024-02-02T16:33:54Z [debug] event not relevant: "/cron-schedule/config": CREATE
+2024-02-02T16:33:54Z [debug] event not relevant: "/cron-schedule/..2024_02_02_16_26_17.3874177937": REMOVE
+2024-02-02T16:45:00Z [verbose] starting reconciler run
+2024-02-02T16:45:00Z [debug] NewReconcileLooper - inferred connection data
+2024-02-02T16:45:00Z [debug] listing IP pools
+2024-02-02T16:45:00Z [debug] no IP addresses to cleanup
+2024-02-02T16:45:00Z [verbose] reconciler success
 ----