Skip to content

Add more control over network configs - #22

Merged
cardoe merged 5 commits into
rackerlabs:mainfrom
prwhitaker:config_control
May 19, 2026
Merged

cardoe merged 5 commits into
rackerlabs:mainfrom
prwhitaker:config_control

Conversation

@prwhitaker

Copy link
Copy Markdown
Contributor

Following the experience of using images created for newer versions of VCF, this PR introduces more control over the network setup that the esxi_netinit python code will generate.

It makes the following changes:

  • default to only creating single vSwitch, portgroup & vmkernel, using the default VMware names for those items (gives out of the box compatibility with VCF 9)
  • allow extra configuration to be controlled via userdata (whether to create additional network config & custom names for the management network items)

It also fixes a bug where the ESXi kickstart config was intended to reboot the host after executing the esxi_netinit code, but failed to do so (which leaves hosts in a state where when they are subsequently rebooted, they lose all network config)

@cardoe
cardoe merged commit f2b150c into rackerlabs:main May 19, 2026
2 checks passed
@prwhitaker
prwhitaker deleted the config_control branch July 17, 2026 09:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants