Date: Fri, 29 Mar 2024 01:49:25 +0000 (UTC) Message-ID: <436390724.823.1711676965421@c4e992b7d277> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_822_1749598209.1711676965420" ------=_Part_822_1749598209.1711676965420 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Metal3IO provides a way for provisioning baremetal hosts using C= lusterAPI in Kubernetes. The whole flow of host provisioning from Cluster A= PI to metal3 assumes the network setup is not their task and operator shoul= d provide a relevant cloud init for baremetal host to setup the network. Th= is assumption works easily for DHCP enabled interfaces but in real scenario= s there can be multiple networks of different types and some of them might = not have any DHCP enabled. In these scenarios we need an IP Address Managem= ent (IPAM) scheme to statically allocate the IP addresses for each interfac= e of each host. This document will collect the requirements for IPAM and pr= ovide a possible solution for its implementation.