- Fix: do not try to delete a LoadBalancer that does not exist ([#105777](https://github.com/kubernetes/kubernetes/pull/105777), [@nilo19](https://github.com/nilo19))

        domainController = Config.getProperty("jcifs.smb1.http.domainController");
        if (domainController == null) {
            domainController = defaultDomain;
            loadBalance = Config.getBoolean("jcifs.smb1.http.loadBalance", true);
        }
        enableBasic = Boolean.parseBoolean(Config.getProperty("jcifs.smb1.http.enableBasic"));

        domainController = Config.getProperty("jcifs.smb1.http.domainController");
        if (domainController == null) {
            domainController = defaultDomain;
            loadBalance = Config.getBoolean("jcifs.smb1.http.loadBalance", true);
        }
        enableBasic = Boolean.parseBoolean(Config.getProperty("jcifs.smb1.http.enableBasic"));

            if (this.domainController == null) {
                this.domainController = this.defaultDomain;
                this.loadBalance = Config.getBoolean(p, "jcifs.http.loadBalance", true);
            }
            this.enableBasic = Boolean.parseBoolean(p.getProperty("jcifs.http.enableBasic"));

            if (this.domainController == null) {
                this.domainController = this.defaultDomain;
                this.loadBalance = Config.getBoolean(p, "jcifs.http.loadBalance", true);
            }
            this.enableBasic = Boolean.parseBoolean(p.getProperty("jcifs.http.enableBasic"));

. {
  etcd churchofminio.com {
      endpoint http://localhost:2379 http://localhost:4001
      upstream /etc/resolv.conf
  }
  debug
  prometheus
  cache 160 mydomain.com
  loadbalance
  forward . /etc/resolv.conf

- Fixed an issue where the Service LoadBalancer controller was not correctly considering the `service.Status new IPMode` field and excluding the Ports when checking if the status was changed, resulting in the changed field potentially not to update the `service.Status` correctly. ([#125225]...

- Fixes the kubelet's ability to restart static pods (#105075, @rphillips) [SIG Node and Testing]
- Kube-proxy(ipvs mode) : delete stale conntrack UDP entries for loadbalancer ingress IP. (#105650, @VivekThrivikraman-est) [SIG Network]
- Release-note Removed error message label from kubelet_started_pods_errors_total metric (#105213, @yxxhero) [SIG Instrumentation and Node]

## Dependencies

        initParams.put("jcifs.smb.client.domain", "TEST_DOMAIN");
        // Don't set domainController to avoid real connection attempts
        initParams.put("jcifs.http.loadBalance", "false");
        initParams.put("jcifs.http.enableBasic", "false");

        when(filterConfig.getInitParameterNames()).thenReturn(Collections.enumeration(initParams.keySet()));

- Kube-proxy, when using a Service with External or LoadBalancer IPs on UDP services , was consuming a large amount of CPU because it was not filtering by the Service destination port and trying to delete all the UDP entries associated to the service. ([#130505](https://github.com/kubernetes/kubernetes/pull/130505),...