mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
100 lines
3.2 KiB
Plaintext
100 lines
3.2 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * networking/multiple_networks/secondary_networks/configuring-ip-secondary-nwt.adoc
|
|
// * networking/hardware_networks/configuring-sriov-net-attach.adoc
|
|
// * networking/hardware_networks/configuring-sriov-ib-attach.adoc
|
|
|
|
:_mod-docs-content-type: REFERENCE
|
|
[id="nw-multus-whereabouts_{context}"]
|
|
= Dynamic IP address assignment configuration with Whereabouts
|
|
|
|
[role="_abstract"]
|
|
The Whereabouts CNI plugin helps the dynamic assignment of an IP address to a secondary network without the use of a DHCP server.
|
|
|
|
The Whereabouts CNI plugin also supports overlapping IP address ranges and configuration of the same CIDR range multiple times within separate `NetworkAttachmentDefinition` CRDs. This provides greater flexibility and management capabilities in multitenant environments.
|
|
|
|
[id="dynamic-ip-address-assignment-objects_{context}"]
|
|
== Dynamic IP address configuration parameters
|
|
|
|
The following table describes the configuration objects for dynamic IP address assignment with Whereabouts:
|
|
|
|
.`ipam` whereabouts configuration parameters
|
|
[cols=".^2,.^2,.^6",options="header"]
|
|
|====
|
|
|Field|Type|Description
|
|
|
|
|`type`
|
|
|`string`
|
|
|The IPAM address type. The value `whereabouts` is required.
|
|
|
|
|`range`
|
|
|`string`
|
|
|An IP address and range in CIDR notation. IP addresses are assigned from within this range of addresses.
|
|
|
|
|`exclude`
|
|
|`array`
|
|
|Optional: A list of zero or more IP addresses and ranges in CIDR notation. IP addresses within an excluded address range are not assigned.
|
|
|
|
|`network_name`
|
|
|`string`
|
|
| Optional: Helps ensure that each group or domain of pods gets its own set of IP addresses, even if they share the same range of IP addresses. Setting this field is important for keeping networks separate and organized, notably in multi-tenant environments.
|
|
|
|
|====
|
|
|
|
[id="dynamic-ip-address-assignment-whereabouts_{context}"]
|
|
== Dynamic IP address assignment configuration with Whereabouts that excludes IP address ranges
|
|
|
|
The following example shows a dynamic address assignment configuration in a NAD file that uses Whereabouts:
|
|
|
|
.Whereabouts dynamic IP address assignment that excludes specific IP address ranges
|
|
[source,json]
|
|
----
|
|
{
|
|
"ipam": {
|
|
"type": "whereabouts",
|
|
"range": "192.0.2.192/27",
|
|
"exclude": [
|
|
"192.0.2.192/30",
|
|
"192.0.2.196/32"
|
|
]
|
|
}
|
|
}
|
|
----
|
|
|
|
[id="dynamic-ip-address-assignment-whereabouts-overlapping-ip-ranges_{context}"]
|
|
== Dynamic IP address assignment that uses Whereabouts with overlapping IP address ranges
|
|
|
|
The following example shows a dynamic IP address assignment that uses overlapping IP address ranges for multitenant networks.
|
|
|
|
.NetworkAttachmentDefinition 1
|
|
[source,json]
|
|
----
|
|
{
|
|
"ipam": {
|
|
"type": "whereabouts",
|
|
"range": "192.0.2.192/29",
|
|
"network_name": "example_net_common",
|
|
}
|
|
}
|
|
----
|
|
|
|
where:
|
|
|
|
`network_name`:: Optional parameter. If set, must match the `network_name` of `NetworkAttachmentDefinition 2`.
|
|
|
|
.NetworkAttachmentDefinition 2
|
|
[source,json]
|
|
----
|
|
{
|
|
"ipam": {
|
|
"type": "whereabouts",
|
|
"range": "192.0.2.192/24",
|
|
"network_name": "example_net_common",
|
|
}
|
|
}
|
|
----
|
|
|
|
where:
|
|
|
|
`network_name`:: Optional parameter. If set, must match the `network_name` of `NetworkAttachmentDefinition 1`.
|