assertDoesNotThrow(() -> channelManager.shutdown());
    }

    @Test
    void testLoadBalancerAccess() {
        ChannelLoadBalancer balancer = channelManager.getLoadBalancer();
        assertNotNull(balancer);

        // Should return same instance
        assertSame(balancer, channelManager.getLoadBalancer());
    }

    @Test
    void testChannelFailureHandling() throws UnknownHostException {

import jcifs.internal.smb2.io.Smb2WriteRequest;

/**
 * Load balancer for SMB3 Multi-Channel connections
 */
public class ChannelLoadBalancer {

    private final ChannelManager manager;
    private LoadBalancingStrategy strategy;
    private final AtomicInteger roundRobinCounter;

    /**
     * Create channel load balancer
     *
     * @param manager channel manager
     */

    manager.addChannel(channel2);
    
    // Test load balancer selection
    ChannelLoadBalancer balancer = new ChannelLoadBalancer(manager);
    
    // Large transfer should prefer high-bandwidth channel
    Smb2ReadRequest largeRead = new Smb2ReadRequest();
    largeRead.setLength(10485760);  // 10MB
    
    ChannelInfo selected = balancer.selectChannel(largeRead);

        // Note: isUseMultiChannel() checks if actual multi-channel is negotiated with server
        // In mock environment, this will be false until we mock successful negotiation

        // Verify load balancer is initialized
        assertNotNull(channelManager.getLoadBalancer());
    }

    @Test
    void testNetworkInterfaceInfo() throws Exception {
        // Test NetworkInterfaceInfo creation and scoring

     *
     * @return true if enabled
     */
    public boolean isUseMultiChannel() {
        return multiChannelEnabled;
    }

    /**
     * Get the load balancer
     *
     * @return load balancer instance
     */
    public ChannelLoadBalancer getLoadBalancer() {
        return loadBalancer;
    }

    /**
     * Get all channels
     *

 *           // Services have been initialized and are healthy, start accepting requests...
 *         }
 *         public void failure(Service service) {
 *           // Something failed, at this point we could log it, notify a load balancer, or take
 *           // some other action.  For now we will just exit.
 *           System.exit(1);
 *         }
 *       },
 *       MoreExecutors.directExecutor());
 *

 *           // Services have been initialized and are healthy, start accepting requests...
 *         }
 *         public void failure(Service service) {
 *           // Something failed, at this point we could log it, notify a load balancer, or take
 *           // some other action.  For now we will just exit.
 *           System.exit(1);
 *         }
 *       },
 *       MoreExecutors.directExecutor());
 *

unauthenticated. The mitigation may be disabled by setting the `UnauthenticatedHTTP2DOSMitigation` feature gate to `false` (it is enabled by default). An API server fronted by an L7 load balancer that already mitigates these http/2 attacks may choose to disable the kube-apiserver mitigation to avoid disrupting load balancer -> kube-apiserver connections if http/2 requests from multiple clients share the same backend connection. An API server on a private network may opt to disable the kube-apiserver mitigation...

- [KCCM] drop filtering nodes for the providerID when syncing load balancers, but have changes to the field trigger a re-sync of load balancers. This should ensure that cloud providers which don't specify providerID, can still use the service controller implementation to provision load balancers. ([#117602](https://github.com/kubernetes/kubernetes/pull/117602), [@alexanderConstantinescu](https://github.com/alexanderConstantinescu))...

- Windows Kubeproxy will use the update load balancer API for load balancer updates, instead of the previous delete and create APIs.