Windows Tanzu Kubernetes Grid requires manual renewal in case DHCP lease time has passed
search cancel

Windows Tanzu Kubernetes Grid requires manual renewal in case DHCP lease time has passed

book

Article ID: 340457

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Symptoms:

When a Windows node's workload DHCP lease expires, the br-int interface does not automatically get a new IP address. This issue has been observed in TKGm <=2.5 using Windows custom machine image.

Environment

VMware Tanzu Kubernetes Grid 2.4.0
VMware Tanzu Kubernetes Grid 2.3.0

Cause


The br-int has had the DHCP client disabled since the creation of the interface.

Resolution


TKGm engineering team is working on finding a fix. This issue will be fixed in the future TKGm release version.

Workaround:

To renew the expired lease, it's required to manually enable the DHCP client in the br-int interface on the Windows node.
 

Enable the DHCP client in the br-int interface running the following Powershell command from the Windows node after the new Windows node creation :

Set-NetIPInterface -InterfaceAlias 'br-int' -Dhcp Enabled



Additional Information

Impact/Risks:
Windows node may lost the IP and the original IP could be assigned to another VM