This is putting cgroup v1 into a deprecated state. ([#134298](https://github.com/kubernetes/kubernetes/pull/134298), [@kannon92](https://github.com/kannon92)) [SIG Node]

- Kube-proxy no longer falls back from ipvs mode to iptables mode if you ask it to do ipvs but the system is not correctly configured. Instead, it will just exit with an error. ([#111806](https://github.com/kubernetes/kubernetes/pull/111806), [@danwinship](https://github.com/danwinship)) [SIG Network]

  Fixes #135757 ([#135759](https://github.com/kubernetes/kubernetes/pull/135759), [@Abhigyan-Shekhar](https://github.com/Abhigyan-Shekhar)) [SIG API Machinery and CLI]

		if ipV4s[i].IsLoopback() {
			return false
		}
		if ipV4s[j].IsLoopback() {
			return true
		}
		return []byte(ipV4s[i].To4())[3] > []byte(ipV4s[j].To4())[3]
	})

	var ips []string
	for _, ip := range ipV4s {
		ips = append(ips, ip.String())
	}

	return append(nonIPs, ips...)
}

func getConsoleEndpoints() (consoleEndpoints []string) {

  slightly stricter about what values will be accepted as IP addresses and network
  address ranges (“CIDR blocks”).
  
  In particular, octets within IPv4 addresses are not allowed to have any leading
  `0`s, and IPv4-mapped IPv6 values (e.g. `::ffff:192.168.0.1`) are forbidden.
  These sorts of values can potentially cause security problems when different

- Fixed an issue in the Windows kube-proxy (winkernel) where IPv4 and IPv6 Service load balancers could be incorrectly shared, causing broken dual-stack Service behavior. The kube-proxy now tracks load balancers per IP family, enabling correct support for PreferDualStack and RequireDualStack Services on Windows nodes....

        assertEquals("http://127.0.0.1:8080", IpAddressUtil.buildUrl("http", ipv4, 8080, null));

        // IPv4 without port
        assertEquals("http://127.0.0.1", IpAddressUtil.buildUrl("http", ipv4, 0, ""));
        assertEquals("http://127.0.0.1", IpAddressUtil.buildUrl("http", ipv4, -1, ""));

        // IPv6 with port and path
        InetAddress ipv6 = InetAddress.getByName("::1");

    }

    @Test
    void testAddIPAddresses() throws Exception {
        InetAddress ipv4 = InetAddress.getByName("192.168.1.100");
        InetAddress ipv6 = InetAddress.getByName("2001:db8::1");

        notification.addNewIPAddress(ipv4);
        notification.addNewIPAddress(ipv6);
        notification.addOldIPAddress(ipv4);

        List<WitnessNotification.WitnessIPAddress> newAddresses = notification.getNewIPAddresses();

 *   <dt>An IPv6 "IPv4 mapped" address, {@code "::ffff:192.168.0.1"}.
 *   <dd>{@code 00 00 00 00 00 00 00 00 00 00 ff ff c0 a8 00 01}
 * </dl>
 *
 * <p>A few notes about IPv6 "IPv4 mapped" addresses and their observed use in Java.
 *
 * <p>"IPv4 mapped" addresses were originally a representation of IPv4 addresses for use on an IPv6
 * socket that could receive both IPv4 and IPv6 connections (by disabling the {@code IPV6_V6ONLY}

        }

        /**
         * Checks if this is an IPv4 address.
         *
         * @return true if IPv4
         */
        public boolean isIPv4() {
            return (flags & IPV4) != 0;
        }

        /**
         * Checks if this is an IPv6 address.
         *
         * @return true if IPv6
         */
        public boolean isIPv6() {