// allocated for services with type LoadBalancer.  Default is "true". It
  // may be set to "false" if the cluster load-balancer does not rely on
  // NodePorts.  If the caller requests specific NodePorts (by specifying a
  // value), those requests will be respected, regardless of this field.
  // This field may only be set for services with type LoadBalancer and will
  // be cleared if the type is changed to any other type.

- Fix IPv6 addresses lost issue in pure ipv6 vsphere environment ([#86001](https://github.com/kubernetes/kubernetes/pull/86001), [@hubv](https://github.com/hubv)) [SIG Cloud Provider]
- Fix LoadBalancer rule checking so that no unexpected LoadBalancer updates are made ([#85990](https://github.com/kubernetes/kubernetes/pull/85990), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider]

- Automatic allocation of NodePorts for services with type LoadBalancer can now be disabled by setting the (new) parameter

- Fixed the following 
  -  AWS Cloud Provider attempts to delete LoadBalancer security group it didn’t provision

## Changelog since v1.17.16

## Changes by Kind

### Bug or Regression

- Fix counting error in service/nodeport/loadbalancer quota check ([#97830](https://github.com/kubernetes/kubernetes/pull/97830), [@pacoxu](https://github.com/pacoxu)) [SIG API Machinery and Network]

- Setting the `status.loadBalancer` of a Service whose `spec.type` is not `LoadBalancer` was previously allowed, but any update to the `metadata` or `spec` would wipe that field. Setting this field is no longer permitted unless `spec.type` is  `LoadBalancer`.  In the very unlikely event that this has unexpected impact, you can enable the `AllowServiceLBStatusOnNonLB` feature gate, which will...

- If Openstack LoadBalancer is not defined in cloud config, the loadbalancer will no longer beis not initialized. any more in openstack. All setups must have some setting under that section for the OpenStack provider. ([#65781](https://github.com/kubernetes/kubernetes/pull/65781), [@zetaab](http...

* Services of type=LoadBalancer which have no endpoints will now immediately ICMP reject connections, rather than time out. ([#74394](https://github.com/kubernetes/kubernetes/pull/74394), [@thockin](https://github.com/thockin))

- Kube-proxy: delete stale conntrack UDP entries for loadbalancer ingress IP. ([#104151](https://github.com/kubernetes/kubernetes/pull/104151), [@aojea](https://github.com/aojea)) [SIG Network]

- Fixed the following 
  -  AWS Cloud Provider attempts to delete LoadBalancer security group it didn’t provision