val InetSocketAddress.socketHost: String get() {
      // The InetSocketAddress was specified with a string (either a numeric IP or a host name). If
      // it is a name, all IPs for that name should be tried. If it is an IP address, only that IP
      // address should be tried.
      val address = address ?: return hostName

-nx????455ses--nx?5mzt5--nx?69vqhr--nx?7&8a4d5a4prebgm--nx?rb2c--nx??a!.&gro?jbo,mo&c?n??oc?ten??vd??b!.&0?1?2?3?4?5?6?7?8?9?a?b?c?d?e?f?g?h?i?j?k?l?m?n?o?p?q?r?s?t?u?v?w?x?y!srab,?z???c!b?za9a0cbgm--nx??e!.&ca?em!an??gro?ics?lim?moc?nue?ofni?t&en?rops??ude?v&og?t???a??g!.&gro?hsadtob,lenap:.nomead,,oc?saak,t&en?ikcats,?ylp.6d,??i&a?v??k!.&gro?lim?moc?su,ten?ude?vog?xx,??m!.&drp?gro?lim?mo&c?n??oc?ude?vog??pk??n!.&clp,dtl,eman?gro?hcs?i!bom??l&im?oc,?m&oc?rif,?neg,ogn,ten?ude?vog?zib:.&gl,ld,no,...

            + "^\\s*msnim:|" //
            + "^\\s*news:|" //
            + "^\\s*tel:|" //
            + "^\\s*unsaved:|" //
            + "^\\s*data:|" //
            + "^\\s*android-app:|" //
            + "^\\s*ios-app:|" //
            + "^\\s*callto:", Pattern.CASE_INSENSITIVE);

    /** Thread-local XPathAPI instance for thread-safe XPath operations. */
    private final ThreadLocal<XPathAPI> xpathAPI = new ThreadLocal<>();

- 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),...

				"application/oda",
				"application/oebps-package+xml",
				"application/ogg",
				"application/kate",
				"application/onenote",
				"application/parityfec",
				"application/patch-ops-error+xml",
				"application/pgp-encrypted",
				"application/pgp-keys",
				"application/pgp-signature",
				"application/pics-rules",
				"application/pidf+xml",
				"application/pidf-diff+xml",

Distributions or administrators of Kubernetes may want to control that new Service CIDRs added to the cluster do not overlap with other networks on the cluster, that only belong to a specific range of IPs. Administrators may also prefer to retain the existing behavior of only having one ServiceCIDR per cluster. You can use `ValidatingAdmissionPolicy` to achieve this. ([#128971](https://github.com/kubernetes/kubernetes/pull/128971), [@aojea](https://github.com/aojea))...

    <sub-class-of type="application/vnd.ms-cab-compressed" />
  </mime-type>

  <mime-type type="application/parityfec"/>
  <mime-type type="application/patch-ops-error+xml">
    <glob pattern="*.xer"/>
  </mime-type>

  <mime-type type="application/pdf">
    <alias type="application/x-pdf"/>
    <acronym>PDF</acronym>
    <_comment>Portable Document Format</_comment>

- KEP-1880: Users of the new feature to add multiple service CIDR will use by default a dual-write strategy on the new ClusterIP allocators to avoid the problem of possible duplicate IPs allocated to Services when running skewed kube-apiservers using different allocators. They can opt-out of this behavior by enabled the feature gate DisableAllocatorDualWrite. ([#122047](https://github.com/kubernetes/kubernetes/pull/122047), [@aojea...