[network-gateway] Node can't get address from DHCP due to error "no address available"

Preflight Checklist

• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for an issue that matches the one I want to file, without success.

Version

v1.56.6

Expected Behavior

Node can always receive ip address.

Actual Behavior

If there are nodes in a cluster that constantly recreated or there are a lot of scaling operations, then DHCP server can run out of available addresses.

Steps To Reproduce

No response

Additional Information

Values are hardcoded or evaluated:

  rows.append('dhcp-range=' + ','.join(args) + ",24h")
...
  netCalc = ipcalc.Network(config['subnet'])
  network['pool']    = str(netCalc.host_first() + 49) + ',' + str(netCalc.host_last())
  network['netmask'] = str(netCalc.netmask())
  network['router']  = str(netCalc.host_first())

Logs

kubectl -n d8-network-gateway logs dhcp-0 --tail 30
Defaulted container "dhcp" out of: dhcp, render-etc-hosts-with-cluster-domain-aliases (init), init (init)
dnsmasq-dhcp: DHCPDISCOVER(ens224) 00:50:56:b9:a8:d5 no address available
dnsmasq-dhcp: DHCPDISCOVER(ens224) 00:50:56:b9:a8:d5 no address available
dnsmasq-dhcp: DHCPDISCOVER(ens224) 00:50:56:b9:a8:d5 no address available
dnsmasq-dhcp: DHCPDISCOVER(ens224) 00:50:56:b9:a8:d5 no address available
dnsmasq-dhcp: DHCPDISCOVER(ens224) 00:50:56:b9:86:ad no address available
dnsmasq-dhcp: DHCPDISCOVER(ens224) 00:50:56:b9:a8:d5 no address available
dnsmasq-dhcp: DHCPDISCOVER(ens224) 00:50:56:b9:7e:61 no address available
dnsmasq-dhcp: DHCPDISCOVER(ens224) 00:50:56:b9:a8:d5 no address available
dnsmasq-dhcp: DHCPDISCOVER(ens224) 00:50:56:b9:86:ad no address available
dnsmasq-dhcp: DHCPDISCOVER(ens224) 00:50:56:b9:a8:d5 no address available
dnsmasq-dhcp: DHCPDISCOVER(ens224) 00:50:56:b9:7e:61 no address available
dnsmasq-dhcp: DHCPDISCOVER(ens224) 00:50:56:b9:86:ad no address available