Allows setting any FQDN as the pod's hostname

[HirazawaUi]

Enhancement Description

• One-line enhancement description (can be used as a release note): Allows users to set any FQDN as the hostname of a pod
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-network/4762-allow-arbitrary-fqdn-as-pod-hostname/README.md
• Discussion Link: Support for arbitrary FQDN as hostname inside a pod kubernetes#97662
• Primary contact (assignee): @HirazawaUi
• Responsible SIGs: network
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.34
  • Beta release target (x.y): 1.35
  • Stable release target (x.y):
• Alpha 1.34
  • KEP (k/enhancements) update PR(s): KEP-4762: Allows setting any FQDN as the pod's hostname #4768
  • Code (k/k) update PR(s):
    • KEP-4762: Allows setting any FQDN as the pod's hostname kubernetes#132558
    • Fix incorrect validation on the kubelet kubernetes#133254
  • Docs (k/website) update PR(s): Add documentation for the HostnameOverride feature gate website#51414
• Beta 1.35
  • KEP (k/enhancements) update PR(s): KEP-4762: Promote to beta stage #5636
  • Code (k/k) update PR(s):
  • Docs (k/website) update(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[HirazawaUi]

/sig network

[aojea]

Is not a duplicate of #1797 ?

[HirazawaUi]

Is not a duplicate of #1797 ?

The goal of this kep is to allow arbitrary FQDN to be set as hostname for pod, #1797 only allows setting pod hostname to FQDN.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale