Given a setup containing Cluster API with VMware (CAPV) and Talos (CABPT / CACPPT ) and IPAM InCluster then IP addresses can be allocated of pool of IP addresses.
The field addressesFromPools in VSphereMachineTemplate specify which pool to use.
CAPV generates the guestinfo.metadata with an IP address from the pool for each virtual machine, however, Talos does not read guestinfo.metadata.
The Talos implementation of integration with VMware platform should be like the nocloud implementation where guestinfo.metadata is used and injected into the virtual machine's network configuration.
Description
Here is a sample of guestinfo.metadata produced by CAPV:
Feature Request
Given a setup containing Cluster API with VMware (CAPV) and Talos (CABPT / CACPPT ) and IPAM InCluster then IP addresses can be allocated of pool of IP addresses. The field
addressesFromPools
inVSphereMachineTemplate
specify which pool to use.CAPV generates the
guestinfo.metadata
with an IP address from the pool for each virtual machine, however, Talos does not readguestinfo.metadata
.The Talos implementation of integration with VMware platform should be like the
nocloud
implementation whereguestinfo.metadata
is used and injected into the virtual machine's network configuration.Description
Here is a sample of
guestinfo.metadata
produced by CAPV:The
nocloud
implementation of reading and usingguestinfo.metadata
could be reused in the VMware platform. metadata.goWhy is this needed?
See detailed explaination here IPAM support proposal