diff --git a/keps/prod-readiness/sig-network/4762.yaml b/keps/prod-readiness/sig-network/4762.yaml
index 38fb70c6754..6e9112666cc 100644
--- a/keps/prod-readiness/sig-network/4762.yaml
+++ b/keps/prod-readiness/sig-network/4762.yaml
@@ -1,3 +1,5 @@
 kep-number: 4762
 alpha:
   approver: "@soltysh"
+beta:
+  approver: "@soltysh"
diff --git a/keps/sig-network/4762-allow-arbitrary-fqdn-as-pod-hostname/README.md b/keps/sig-network/4762-allow-arbitrary-fqdn-as-pod-hostname/README.md
index 0a9b0d947db..3d3df2c0e0f 100644
--- a/keps/sig-network/4762-allow-arbitrary-fqdn-as-pod-hostname/README.md
+++ b/keps/sig-network/4762-allow-arbitrary-fqdn-as-pod-hostname/README.md
@@ -1,81 +1,4 @@
-<!--
-**Note:** When your KEP is complete, all of these comment blocks should be removed.
-
-To get started with this template:
-
-- [ ] **Pick a hosting SIG.**
-  Make sure that the problem space is something the SIG is interested in taking
-  up. KEPs should not be checked in without a sponsoring SIG.
-- [ ] **Create an issue in kubernetes/enhancements**
-  When filing an enhancement tracking issue, please make sure to complete all
-  fields in that template. One of the fields asks for a link to the KEP. You
-  can leave that blank until this KEP is filed, and then go back to the
-  enhancement and add the link.
-- [ ] **Make a copy of this template directory.**
-  Copy this template into the owning SIG's directory and name it
-  `NNNN-short-descriptive-title`, where `NNNN` is the issue number (with no
-  leading-zero padding) assigned to your enhancement above.
-- [ ] **Fill out as much of the kep.yaml file as you can.**
-  At minimum, you should fill in the "Title", "Authors", "Owning-sig",
-  "Status", and date-related fields.
-- [ ] **Fill out this file as best you can.**
-  At minimum, you should fill in the "Summary" and "Motivation" sections.
-  These should be easy if you've preflighted the idea of the KEP with the
-  appropriate SIG(s).
-- [ ] **Create a PR for this KEP.**
-  Assign it to people in the SIG who are sponsoring this process.
-- [ ] **Merge early and iterate.**
-  Avoid getting hung up on specific details and instead aim to get the goals of
-  the KEP clarified and merged quickly. The best way to do this is to just
-  start with the high-level sections and fill out details incrementally in
-  subsequent PRs.
-
-Just because a KEP is merged does not mean it is complete or approved. Any KEP
-marked as `provisional` is a working document and subject to change. You can
-denote sections that are under active debate as follows:
-
-```
-<<[UNRESOLVED optional short context or usernames ]>>
-Stuff that is being argued.
-<<[/UNRESOLVED]>>
-```
-
-When editing KEPS, aim for tightly-scoped, single-topic PRs to keep discussions
-focused. If you disagree with what is already in a document, open a new PR
-with suggested changes.
-
-One KEP corresponds to one "feature" or "enhancement" for its whole lifecycle.
-You do not need a new KEP to move from beta to GA, for example. If
-new details emerge that belong in the KEP, edit the KEP. Once a feature has become
-"implemented", major changes should get new KEPs.
-
-The canonical place for the latest set of instructions (and the likely source
-of this file) is [here](/keps/NNNN-kep-template/README.md).
-
-**Note:** Any PRs to move a KEP to `implementable`, or significant changes once
-it is marked `implementable`, must be approved by each of the KEP approvers.
-If none of those approvers are still appropriate, then changes to that list
-should be approved by the remaining approvers and/or the owning SIG (or
-SIG Architecture for cross-cutting KEPs).
--->
 # KEP-4762: Allows setting arbitrary FQDN as the pod's hostname
-
-<!--
-This is the title of your KEP. Keep it short, simple, and descriptive. A good
-title can help communicate what the KEP is and should be considered as part of
-any review.
--->
-
-<!--
-A table of contents is helpful for quickly jumping to sections of a KEP and for
-highlighting any additional information provided beyond the standard KEP
-template.
-
-Ensure the TOC is wrapped with
-  <code>&lt;!-- toc --&rt;&lt;!-- /toc --&rt;</code>
-tags, and then generate with `hack/update-toc.sh`.
--->
-
 <!-- toc -->
 - [Release Signoff Checklist](#release-signoff-checklist)
 - [Summary](#summary)
@@ -133,8 +56,8 @@ Items marked with (R) are required *prior to targeting to a milestone / release*
 - [x] (R) Enhancement issue in release milestone, which links to KEP dir in [kubernetes/enhancements] (not the initial KEP PR)
 - [x] (R) KEP approvers have approved the KEP status as `implementable`
 - [x] (R) Design details are appropriately documented
-- [ ] (R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input (including test refactors)
-  - [ ] e2e Tests for all Beta API Operations (endpoints)
+- [x] (R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input (including test refactors)
+  - [x] e2e Tests for all Beta API Operations (endpoints)
   - [ ] (R) Ensure GA e2e tests meet requirements for [Conformance Tests](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/conformance-tests.md) 
   - [ ] (R) Minimum Two Week Window for GA e2e tests to prove flake free
 - [ ] (R) Graduation criteria is in place
@@ -142,7 +65,7 @@ Items marked with (R) are required *prior to targeting to a milestone / release*
 - [ ] (R) Production readiness review completed
 - [ ] (R) Production readiness review approved
 - [ ] "Implementation History" section is up-to-date for milestone
-- [ ] User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
+- [x] User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
 - [ ] Supporting documentation—e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes
 
 <!--
@@ -265,60 +188,16 @@ As shown in the table, setting `hostnameOverride` will only change the hostname
 
 ### Graduation Criteria
 
-<!--
-**Note:** *Not required until targeted at a release.*
-
-Define graduation milestones.
-
-These may be defined in terms of API maturity, [feature gate] graduations, or as
-something else. The KEP should keep this high-level with a focus on what
-signals will be looked at to determine graduation.
-
-Consider the following in developing the graduation criteria for this enhancement:
-- [Maturity levels (`alpha`, `beta`, `stable`)][maturity-levels]
-- [Feature gate][feature gate] lifecycle
-- [Deprecation policy][deprecation-policy]
-
-Clearly define what graduation means by either linking to the [API doc
-definition](https://kubernetes.io/docs/concepts/overview/kubernetes-api/#api-versioning)
-or by redefining what graduation means.
-
-In general we try to use the same stages (alpha, beta, GA), regardless of how the
-functionality is accessed.
-
-[feature gate]: https://git.k8s.io/community/contributors/devel/sig-architecture/feature-gates.md
-[maturity-levels]: https://git.k8s.io/community/contributors/devel/sig-architecture/api_changes.md#alpha-beta-and-stable-versions
-[deprecation-policy]: https://kubernetes.io/docs/reference/using-api/deprecation-policy/
-
-Below are some examples to consider, in addition to the aforementioned [maturity levels][maturity-levels].
-
-**Note:** Generally we also wait at least two releases between beta and
-GA/stable, because there's no opportunity for user feedback, or even bug reports,
-in back-to-back releases.
-
-**For non-optional features moving to GA, the graduation criteria must include
-[conformance tests].**
-
-[conformance tests]: https://git.k8s.io/community/contributors/devel/sig-architecture/conformance-tests.md
-
-#### Deprecation
-
-- Announce deprecation and support policy of the existing flag
-- Two versions passed since introducing the functionality that deprecates the flag (to address version skew)
-- Address feedback on usage/changed behavior, provided on GitHub issues
-- Deprecate the flag
--->
-
 #### Alpha
 
 - Use the `HostnameOverride` feature gate to implement this feature.
 - Initial e2e tests completed and enabled.
+  - The link to the added e2e test: https://github.com/kubernetes/kubernetes/blob/master/test/e2e/common/node/pod_hostnameoverride.go
 - Add documentation for feature gates.
 - Add a detailed table to the docs illustrating the mappings between pod hostnames and DNS records under different configurations.
 
 #### Beta
 
-- Gather feedback from developers and surveys
 - Make feature gate to be enabled by default.
 - Update the feature gate documentation.
 
@@ -342,28 +221,6 @@ Older apiserver versions will similarly ignore the hostnameOverride field:
 
 ## Production Readiness Review Questionnaire
 
-<!--
-
-Production readiness reviews are intended to ensure that features merging into
-Kubernetes are observable, scalable and supportable; can be safely operated in
-production environments, and can be disabled or rolled back in the event they
-cause increased failures in production. See more in the PRR KEP at
-https://git.k8s.io/enhancements/keps/sig-architecture/1194-prod-readiness.
-
-The production readiness review questionnaire must be completed and approved
-for the KEP to move to `implementable` status and be included in the release.
-
-In some cases, the questions below should also have answers in `kep.yaml`. This
-is to enable automation to verify the presence of the review, and to reduce review
-burden and latency.
-
-The KEP must have a approver from the
-[`prod-readiness-approvers`](http://git.k8s.io/enhancements/OWNERS_ALIASES)
-team. Please reach out on the
-[#prod-readiness](https://kubernetes.slack.com/archives/CPNHUMN74) channel if
-you need any help or guidance.
--->
-
 ### Feature Enablement and Rollback
 
 ###### How can this feature be enabled / disabled in a live cluster?
@@ -393,7 +250,7 @@ There will be no impact on running Pods in the cluster. This change solely affec
 
 ###### Are there any tests for feature enablement/disablement?
 
-We will verify proper functionality through unit tests and e2e tests, covering both enabled and disabled states of the feature gate.
+We have added unit tests for enabling and disabling the feature gate in: `pkg/kubelet/kubelet_pods_test.go#TestGeneratePodHostNameAndDomain`
 
 ### Rollout, Upgrade and Rollback Planning
 
@@ -413,7 +270,104 @@ The `kubelet_started_pods_total` metrics helps determine whether enabling/disabl
 
 ###### Were upgrade and rollback tested? Was the upgrade->downgrade->upgrade path tested?
 
-N/A
+I use `FEATURE_GATES=HostnameOverride=true ./hack/local-up-cluster.sh` to create a new cluster.
+
+Check the cluster version:
+```
+$GOPATH/src/k8s.io/kubernetes/_output/bin/kubectl version
+Client Version: v1.35.0
+Kustomize Version: v5.7.1
+Server Version: v1.35.0
+```
+Run a pod that uses HostnameOverride:
+```
+cat <<EOF | $GOPATH/src/k8s.io/kubernetes/_output/bin/kubectl apply -f -
+apiVersion: v1
+kind: Pod
+metadata:
+  name: data-writer-pod
+spec:
+  hostUsers: false
+  hostNetwork: true
+  priorityClassName: system-node-critical
+  containers:
+  - name: writer-container
+    image: busybox
+    command: ["/bin/sh", "-c", "sleep 3600"]
+EOF
+```
+Confirm the pod is running normally and the HostnameOverride feature is working correctly:
+```
+➜  opt $GOPATH/src/k8s.io/kubernetes/_output/bin/kubectl get pods
+NAME       READY   STATUS    RESTARTS   AGE
+test-pod   1/1     Running   0          5s
+➜  opt $GOPATH/src/k8s.io/kubernetes/_output/bin/kubectl exec test-pod -- hostname
+test-hostname
+```
+
+Checkout the `release-1.34` branch, add a tag using `git tag v1.34.0`, rebuild the `kubelet` and `kube-apiserver` binaries, and run kubelet and kube-apiserver using the same local command.
+
+Check the cluster version:
+```
+$GOPATH/src/k8s.io/kubernetes/_output/bin/kubectl version
+Client Version: v1.35.0
+Kustomize Version: v5.7.1
+Server Version: v1.34.0
+```
+Confirm the pod is still running and the HostnameOverride feature is still working correctly:
+
+```
+➜  opt $GOPATH/src/k8s.io/kubernetes/_output/bin/kubectl get pods
+NAME       READY   STATUS    RESTARTS   AGE
+test-pod   1/1     Running   0          3m56s
+➜  opt $GOPATH/src/k8s.io/kubernetes/_output/bin/kubectl exec test-pod -- hostname
+test-hostname
+```
+Delete the pod and recreate it:
+```
+opt $GOPATH/src/k8s.io/kubernetes/_output/bin/kubectl delete test-pod
+pod "test-pod" deleted from default namespace
+
+cat <<EOF | $GOPATH/src/k8s.io/kubernetes/_output/bin/kubectl apply -f -
+apiVersion: v1
+kind: Pod
+metadata:
+  name: data-writer-pod
+spec:
+  hostUsers: false
+  hostNetwork: true
+  priorityClassName: system-node-critical
+  containers:
+  - name: writer-container
+    image: busybox
+    command: ["/bin/sh", "-c", "sleep 3600"]
+EOF
+```
+Confirm the pod is running and the HostnameOverride feature is still working correctly:
+```
+➜  opt $GOPATH/src/k8s.io/kubernetes/_output/bin/kubectl get pods
+NAME       READY   STATUS    RESTARTS   AGE
+test-pod   1/1     Running   0          17s
+➜  opt $GOPATH/src/k8s.io/kubernetes/_output/bin/kubectl exec test-pod -- hostname
+test-hostname
+```
+Checkout to the master branch, add a tag using `git tag v1.35.0`, rebuild the `kubelet` and `kube-apiserver` binaries, and run `kubelet` and `kube-apiserver` using the same local command.
+
+Check the cluster version:
+```
+$GOPATH/src/k8s.io/kubernetes/_output/bin/kubectl version
+Client Version: v1.35.0
+Kustomize Version: v5.7.1
+Server Version: v1.35.0
+```
+Confirm the pod is still running and the HostnameOverride feature is still working correctly:
+```
+$GOPATH/src/k8s.io/kubernetes/_output/bin/kubectl get pods
+NAME       READY   STATUS    RESTARTS   AGE
+test-pod   1/1     Running   0          98s
+➜  opt $GOPATH/src/k8s.io/kubernetes/_output/bin/kubectl exec test-pod -- hostname
+test-hostname
+```
 
 ###### Is the rollout accompanied by any deprecations and/or removals of features, APIs, fields of API types, flags, etc.?
 
@@ -421,57 +375,26 @@ No
 
 ### Monitoring Requirements
 
-<!--
-This section must be completed when targeting beta to a release.
-
-For GA, this section is required: approvers should be able to confirm the
-previous answers based on experience in the field.
--->
-
 ###### How can an operator determine if the feature is in use by workloads?
 
-<!--
-Ideally, this should be a metric. Operations against the Kubernetes API (e.g.,
-checking if there are objects with field X set) may be a last resort. Avoid
-logs or events for this purpose.
--->
+Users can check which workloads are utilizing this feature with the following command:
+```
+kubectl get pods -A -o json | jq -r '.items[] | select(.spec.hostnameOverride != null) | "\(.metadata.namespace) \(.metadata.name) \(.spec.hostnameOverride)"'
+```
 
 ###### How can someone using this feature know that it is working for their instance?
 
-<!--
-For instance, if this is a pod-related feature, it should be possible to determine if the feature is functioning properly
-for each individual pod.
-Pick one more of these and delete the rest.
-Please describe all items visible to end users below with sufficient detail so that they can verify correct enablement
-and operation of this feature.
-Recall that end users cannot usually observe component logs or access metrics.
--->
-
-Validate alignment of `podSpec.hostnameOverride` with the pod's actual hostname using:
-kubectl exec <pod-name> -- hostname
+Users can use the following command to identify which workloads are using this feature and verify whether it is functioning as expected.
+```
+kubectl get pods -A -o json | jq -r '.items[] | select(.spec.hostnameOverride != null) | "\(.metadata.namespace) \(.metadata.name) \(.spec.hostnameOverride)"' | while IFS=' ' read -r ns pod ho; do actual=$(kubectl exec -n "$ns" "$pod" -- hostname 2>/dev/null); [ "$actual" = "$ho" ] && echo "$ns $pod $actual $ho"; done
+```
 
 ###### What are the reasonable SLOs (Service Level Objectives) for the enhancement?
 
-<!--
-This is your opportunity to define what "normal" quality of service looks like
-for a feature.
-
-It's impossible to provide comprehensive guidance, but at the very
-high level (needs more precise definitions) those may be things like:
-  - per-day percentage of API calls finishing with 5XX errors <= 1%
-  - 99% percentile over day of absolute value from (job creation time minus expected
-    job creation time) for cron job <= 10%
-  - 99.9% of /health requests per day finish with 200 code
-
-These goals will help you determine what you need to measure (SLIs) in the next
-question.
--->
+If the `kubelet_started_pods_errors_total` metric in a cluster remains consistently at 0, then after introducing this feature, the value of `kubelet_started_pods_errors_total` should similarly remain at 0.
 
 ###### What are the SLIs (Service Level Indicators) an operator can use to determine the health of the service?
 
-<!--
-Pick one more of these and delete the rest.
--->
 
 - [x] Metrics
   - Metric name: `run_podsandbox_errors_total`, `kubelet_started_pods_total`, `kubelet_started_pods_errors_total`, `kubelet_restarted_pods_total`
@@ -482,33 +405,16 @@ Pick one more of these and delete the rest.
 
 ###### Are there any missing metrics that would be useful to have to improve observability of this feature?
 
-<!--
-Describe the metrics themselves and the reasons why they weren't added (e.g., cost,
-implementation difficulties, etc.).
--->
+No
 
 ### Dependencies
 
-<!--
-This section must be completed when targeting beta to a release.
--->
-
 ###### Does this feature depend on any specific services running in the cluster?
 
 No
 
 ### Scalability
 
-<!--
-For alpha, this section is encouraged: reviewers should consider these questions
-and attempt to answer them.
-
-For beta, this section is required: reviewers must answer these questions.
-
-For GA, this section is required: approvers should be able to confirm the
-previous answers based on experience in the field.
--->
-
 ###### Will enabling / using this feature result in any new API calls?
 
 No
@@ -539,33 +445,13 @@ No
 
 ### Troubleshooting
 
-<!--
-This section must be completed when targeting beta to a release.
-
-For GA, this section is required: approvers should be able to confirm the
-previous answers based on experience in the field.
-
-The Troubleshooting section currently serves the `Playbook` role. We may consider
-splitting it into a dedicated `Playbook` document (potentially with some monitoring
-details). For now, we leave it here.
--->
-
 ###### How does this feature react if the API server and/or etcd is unavailable?
 
+No impact to the running workloads
+
 ###### What are other known failure modes?
 
-<!--
-For each of them, fill in the following information by copying the below template:
-  - [Failure mode brief description]
-    - Detection: How can it be detected via metrics? Stated another way:
-      how can an operator troubleshoot without logging into a master or worker node?
-    - Mitigations: What can be done to stop the bleeding, especially for already
-      running user workloads?
-    - Diagnostics: What are the useful log messages and their required logging
-      levels that could help debug the issue?
-      Not required until feature graduated to beta.
-    - Testing: Are there any tests for failure mode? If not, describe why.
-    -->
+No known failure modes.
 
 ###### What steps should be taken if SLOs are not being met to determine the problem?
 
@@ -573,6 +459,7 @@ For each of them, fill in the following information by copying the below templat
 
 - 2024-07-18: Initial draft KEP
 - 2025-08-13: Align KEPs with implemented PRs and documentation.
+- 2025-10-10: Promote to beta stage
 
 ## Drawbacks
 
diff --git a/keps/sig-network/4762-allow-arbitrary-fqdn-as-pod-hostname/kep.yaml b/keps/sig-network/4762-allow-arbitrary-fqdn-as-pod-hostname/kep.yaml
index 76ab65c0e26..4e0a07d2af3 100644
--- a/keps/sig-network/4762-allow-arbitrary-fqdn-as-pod-hostname/kep.yaml
+++ b/keps/sig-network/4762-allow-arbitrary-fqdn-as-pod-hostname/kep.yaml
@@ -14,12 +14,12 @@ approvers:
   - "@SergeyKanzhelev"
 
 # The target maturity stage in the current dev cycle for this KEP.
-stage: alpha
+stage: beta
 
 # The most recent milestone for which work toward delivery of this KEP has been
 # done. This can be the current (upcoming) milestone, if it is being actively
 # worked on.
-latest-milestone: "v1.34"
+latest-milestone: "v1.35"
 
 # The milestone at which this feature was, or is targeted to be, at each stage.
 milestone: