- Fix isCurrentInstance for Windows by removing the dependency of hostname. ([#89138](https://github.com/kubernetes/kubernetes/pull/89138), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider]

labels.available=状態
labels.createdBy=作成者
labels.createdTime=作成日時
labels.depth=深さ
labels.excludedPaths=クロール対象から除外するパス
labels.excludedUrls=クロール対象から除外するURL
labels.excludedDocPaths=検索対象から除外するパス
labels.excludedDocUrls=検索対象から除外するURL
labels.hostname=ホスト名
labels.id=ID
labels.includedPaths=クロール対象とするパス
labels.includedUrls=クロール対象とするURL
labels.includedDocPaths=検索対象とするパス
labels.includedDocUrls=検索対象とするURL
labels.maxAccessCount=最大アクセス数
labels.name=名前

        <field>
          <name>url</name>
          <version>4.0.0+</version>
          <required>true</required>
          <description>
            The url of the repository, in the form {@code protocol://hostname/path}.
          </description>
          <type>String</type>
        </field>
        <field>
          <name>layout</name>
          <version>4.0.0+</version>
          <description>

 * See {@link TrieParser}.
 *
 * @since 16.0
 */
@GwtCompatible
@Beta
public final class PublicSuffixPatterns {
  private PublicSuffixPatterns() {}

  /** If a hostname is contained as a key in this map, it is a public suffix. */
  public static final ImmutableMap<String, PublicSuffixType> EXACT =
      TrieParser.parseTrie(

*   The kubeadm `--skip-preflight-checks` flag is now deprecated and will be removed in a future release.
*   If you are using the cloud provider API to determine the external host address of the apiserver, set `--external-hostname` explicitly instead. The cloud provider detection has been deprecated and will be removed in the future ([#54516](https://github.com/kubernetes/kubernetes/pull/54516),[ @dims](https://github.com/dims))

### **Multicluster**

* kube-proxy needs to be configured to override hostname in some environments. ([#857](https://github.com/kubernetes/kubeadm/issues/857), [@detiber](https://github.com/detiber))

- Fixed a bug that occurred when the hostname label of a node did not match the node name, pods bound to a PersistentVolume with `nodeAffinity` using the hostname may be scheduled to the wrong node or experience scheduling failures. ([#125398](https://github.com/kubernetes/kubernetes/pull/125398), [@AxeZhan](https://github.com/AxeZhan)) [SIG Scheduling...

- The new test `[sig-network] DNS should now provide /etc/hosts entries for the cluster [LinuxOnly] [Conformance]` will validate the host entries set in the ``/etc/hosts`` file (pod's FQDN and hostname), which should be managed by Kubelet. ([#72729](https://github.com/kubernetes/kubernetes/pull/72729), [@bclau](https://github.com/bclau))

## Changelog since v1.31.2

## Changes by Kind

### Bug or Regression

* Port-forward: use out and error streams instead of glog ([#17030](https://github.com/kubernetes/kubernetes/pull/17030), [@csrwng](https://github.com/csrwng))
* Promote Pod Hostname & Subdomain to fields (were annotations) ([#24362](https://github.com/kubernetes/kubernetes/pull/24362), [@ArtfulCoder](https://github.com/ArtfulCoder))