Supports static IPv4 assignment in VMware Windows OVA

[laozc]

Change description

Supports static IPv4 assignment in VMware Windows OVA

The user may provide these input parameters with image-builder.

{
  "ipv4_address_cidr": "192.168.88.2/24",
  "gateway4": "192.168.88.1",
  "dns_servers": "192.168.88.1"
}

Related issues

• Fixes Static IP assignment support when building VMware Windows OVA #1681

Additional context

Related doc from MSFT
https://learn.microsoft.com/en-us/windows-hardware/customize/desktop/unattend/microsoft-windows-tcpip
https://learn.microsoft.com/en-us/windows-hardware/customize/desktop/unattend/microsoft-windows-dns-client

[mboersma]

/assign @jsturtevant
for a Windows perspective

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from jsturtevant. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[randomvariable]

Will have to take it on trust that this is fine as no longer an expert on unattend.xml

/lgtm

[laozc]

Ping.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-ci-robot]

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.