Skip to content

Commit 5cd9d4f

Browse files
authored
Merge pull request #62511 from stevsmit/OSDOCS-6917-Whereabouts
Updates dynamic IP address assignment configuration with whereabouts …
2 parents fc96740 + 39d96d1 commit 5cd9d4f

File tree

1 file changed

+71
-0
lines changed

1 file changed

+71
-0
lines changed

modules/nw-multus-ipam-object.adoc

Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -240,3 +240,74 @@ Whereabouts can be used for both IPv4 and IPv6 addresses.
240240
ifdef::sr-iov[]
241241
:!sr-iov:
242242
endif::[]
243+
244+
[id="nw-multus-creating-whereabouts-reconciler-daemon-set_{context}"]
245+
== Creating a Whereabouts reconciler daemon set
246+
247+
The Whereabouts reconciler is responsible for managing dynamic IP address assignments for the pods within a cluster using the Whereabouts IP Address Management (IPAM) solution. It ensures that each pods gets a unique IP address from the specified IP address range. It also handles IP address releases when pods are deleted or scaled down.
248+
249+
[NOTE]
250+
====
251+
You can also use a `NetworkAttachmentDefinition` custom resource for dynamic IP address assignment.
252+
====
253+
254+
The Whereabouts reconciler daemon set is automatically created when you configure an additional network through the Cluster Network Operator. It is not automatically created when you configure an additional network from a YAML manifest.
255+
256+
To trigger the deployment of the Whereabouts reconciler daemonset, you must manually create a `whereabouts-shim` network attachment by editing the Cluster Network Operator custom resource file.
257+
258+
Use the following procedure to deploy the Whereabouts reconciler daemonset.
259+
260+
.Procedure
261+
262+
. Edit the `Network.operator.openshift.io` custom resource (CR) by running the following command:
263+
+
264+
[source,terminal]
265+
----
266+
$ oc edit network.operator.openshift.io cluster
267+
----
268+
269+
. Modify the `additionalNetworks` parameter in the CR to add the `whereabouts-shim` network attachment definition. For example:
270+
+
271+
[source,yaml]
272+
----
273+
apiVersion: operator.openshift.io/v1
274+
kind: Network
275+
metadata:
276+
name: cluster
277+
spec:
278+
additionalNetworks:
279+
- name: whereabouts-shim
280+
namespace: default
281+
rawCNIConfig: |-
282+
{
283+
"name": "whereabouts-shim",
284+
"cniVersion": "0.3.1",
285+
"type": "bridge",
286+
"ipam": {
287+
"type": "whereabouts"
288+
}
289+
}
290+
type: Raw
291+
----
292+
293+
. Save the file and exit the text editor.
294+
295+
. Verify that the `whereabouts-reconciler` daemon set deployed successfully by running the following command:
296+
+
297+
[source,terminal]
298+
----
299+
$ oc get all -n openshift-multus | grep whereabouts-reconciler
300+
----
301+
+
302+
.Example output
303+
+
304+
[source,terminal]
305+
----
306+
pod/whereabouts-reconciler-jnp6g 1/1 Running 0 6s
307+
pod/whereabouts-reconciler-k76gg 1/1 Running 0 6s
308+
pod/whereabouts-reconciler-k86t9 1/1 Running 0 6s
309+
pod/whereabouts-reconciler-p4sxw 1/1 Running 0 6s
310+
pod/whereabouts-reconciler-rvfdv 1/1 Running 0 6s
311+
pod/whereabouts-reconciler-svzw9 1/1 Running 0 6s
312+
daemonset.apps/whereabouts-reconciler 6 6 6 6 6 kubernetes.io/os=linux 6s
313+
----

0 commit comments

Comments
 (0)