Repository navigation
Allows setting any FQDN as the pod's hostname #4762
Description
Activity
/sig network
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
- After 90d of inactivity,
/remove-lifecycle stale
95 remaining items
- moved this from At risk for enhancements freeze to Tracked for enhancements freeze in v1.37 Release Tracking
on Jun 13, 2026 Hello @HirazawaUi 👋! v1.37 Docs team here.
Does this enhancement work planned for
v1.37require any new docs or modification to existing docs?If so, please follow the steps here to open a PR against
dev-1.37branch in thek/websiterepo. This PR can be just a placeholder at this time and must be created before Thursday 2nd July 2026 (AoE) / Friday 3rd July 2026, 12:00 UTC.Also, take a look at Documenting for a release to get yourself familiarized with the docs requirement for the release.
Thank you!
Hi @HirazawaUi 👋
This is Christopher Tineo (@TineoC) from the v1.37 Communications Team!
For the v1.37 release, we are in the process of collecting and curating a list of potential feature blogs, and we'd love for you to consider writing one for your enhancement!
As you may be aware, feature blogs are a great way to communicate to users about features which fall into (but not limited to) the following categories:
- This KEP introduces some breaking change(s)
- This KEP has significant impacts and/or implications for Kubernetes users
- ...Or this is a long-awaited feature, in which case a blog would go a long way to cover the journey more in detail.
To opt in to write a feature blog, could you please let us know and open a "Feature Blog placeholder PR" (which can be only a skeleton at first) against the website repository by Friday, July 10, 2026 (02:00 UTC)? For more information about writing a blog, please find the blog contribution guidelines and the feature blog PR instructions for authors.
Some timelines to keep in mind:
- July 10, 2026 (02:00 UTC): Feature blog PR freeze
- August 3, 2026: Feature blogs ready for review
- You can find more in the release document
Note: In your placeholder PR, use the current scheduled overall release date for the blog
dateand add adraft:trueto the front matter. This will help us to merging this ahead of the release date and scheduling it after the release date.For easier tracking, please let us know whether you'd like to opt in or opt out. If you're opting in, kindly include the skeleton blog PR in your reply.
If you have any questions or need help, please feel free to reach out to me or any of the Communications Team members. We are here to help you!
@TineoC This is a very small feature, so I don't think it needs a blog post. Thank you for the reminder.
Reacted by Christopher TineoHey again @HirazawaUi 👋, v1.37 Enhancements team here.
Just checking in as we approach code freeze and test freeze on Wednesday July 22, 2026 (AoE) / Thursday, July 23, 2026, 12:00 UTC.
Here's where this enhancement currently stands:
- All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
- All PRs are ready to be merged (they have
approvedandlgtmlabels applied) by the code freeze deadline. This includes tests.
Per the issue description, these are all of the implementation (code-related) PRs for v1.37, some of which are not merged yet:
Please let me know (and keep the issue description updated) if there are any other PRs in
k/kthat we should track for this KEP, so that we can maintain accurate status.If the implementation work for this enhancement is occurring out-of-tree (i.e., outside of
k/k), please link the relevant PRs in the issue description for visibility. Alternatively, if you're unable to provide specific PR links, a confirmation that all out-of-tree implementation work is complete and merged will help us finalize tracking and maintain accuracy.The status of this enhancement is marked as
At risk for code freeze.If you anticipate missing code freeze, you can file an exception request in advance.
- moved this from Tracked for enhancements freeze to At risk for code freeze in v1.37 Release Tracking
on Jul 18, 2026 - moved this from At risk for code freeze to Tracked for code freeze in v1.37 Release Tracking
on Jul 23, 2026 Hello @HirazawaUi 👋! v1.37 Docs team here,
As we approach:
- Ready to Review deadline: Tuesday 28th July 2026
- Docs Freeze deadline: Wednesday 5th August 2026 (AoE) / Thursday 6th August 2026, 12:00 UTC
Linked Docs PR: kubernetes/website#56191
Here's where this enhancement currently stands:
- The docs PR(s) to the
k/websiterepo that are related to your enhancement are linked in the above issue description (for tracking purposes). - The docs PR(s) is created against the dev-1.37 branch.
- The docs PR(s) are in Ready to Review state wherein they are updated with all the changes required and marked ready to review.
- The docs PR(s) are ready to be merged (they have
approvedandlgtmlabels applied) by the Docs Freeze deadline.
Note
The status of this enhancement is marked as At Risk for Docs Freeze.
If you anticipate missing docs freeze, you can file an exception request in advance.
- moved this from Tracked for code freeze to At Risk for Docs Freeze in v1.37 Release Tracking
on Jul 27, 2026 Note
The status of this enhancement is marked as Tracked for Docs Freeze.
- moved this from At Risk for Docs Freeze to Tracked for Docs Freeze in v1.37 Release Tracking
on Aug 5, 2026 Hi @HirazawaUi 👋, 1.37 Enhancements team here.
Given that this KEP has graduated to
stable, if all the work is completed, could you please update the KEP status inkep.yamltoimplemented, and then close this issue?Thanks!
/remove-label lead-opted-in
/remove-label tracked/yes
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Enhancement Description
hostnameinside a pod kubernetes#97662k/enhancements) update PR(s): KEP-4762: Allows setting any FQDN as the pod's hostname #4768k/k) update PR(s):k/website) update PR(s): Add documentation for the HostnameOverride feature gate website#51414k/enhancements) update PR(s): KEP-4762: Promote to beta stage #5636k/k) update PR(s): kep-4762: Promote HostnameOverride feature gate to beta stage kubernetes#134729k/website) update(s): kep-4762: Add beta stage docs for the HostnameOverride feature gate website#52874k/enhancements) update PR(s): KEP-4762: Promote to GA #6108k/k) update PR(s): KEP-4762: Promote HostnameOverride feature gate to GA kubernetes#139116k/website) update(s): KEP-4762: Update HostnameOverride feature gate to stable website#56191Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.