-
Notifications
You must be signed in to change notification settings - Fork 502
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VMware: Use network information from guestinfo.metadata #6708
Comments
ErikLundJensen
added a commit
to ErikLundJensen/talos
that referenced
this issue
Jan 10, 2023
ErikLundJensen
added a commit
to ErikLundJensen/talos
that referenced
this issue
Jan 13, 2023
The vmware metadata which is setup by CAPV is defined here: |
7 tasks
ErikLundJensen
added a commit
to ErikLundJensen/talos
that referenced
this issue
Jan 21, 2023
ErikLundJensen
added a commit
to ErikLundJensen/talos
that referenced
this issue
Jan 21, 2023
ErikLundJensen
added a commit
to ErikLundJensen/talos
that referenced
this issue
Jan 24, 2023
Add VMware GuestInfo metadata to network configuration. Closes siderolabs#6708 Signed-off-by: Erik Lund Jensen <info@erikjensen.it>
ErikLundJensen
added a commit
to ErikLundJensen/talos
that referenced
this issue
Jan 24, 2023
Add VMware GuestInfo metadata to network configuration. Closes siderolabs#6708 Signed-off-by: Erik Lund <info@erikjensen.it>
ErikLundJensen
added a commit
to ErikLundJensen/talos
that referenced
this issue
Jan 25, 2023
Add VMware GuestInfo metadata to network configuration. Closes siderolabs#6708 Signed-off-by: Erik Lund <info@erikjensen.it>
Adding refernce to PR-6737 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.go
Why is this needed?
See detailed explaination here IPAM support proposal
The text was updated successfully, but these errors were encountered: