Change:
</span></pre><p>The KubeProxyConfiguration type should be used to change the configuration passed to kube-proxy instances deployed in the cluster. If this object is not provided or provided only partially, kubeadm applies defaults.</p> <p>See https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/ or <del> https://godoc.org/k8s.io/kube-proxy/config/v1alpha1#KubeProxyConfiguration </del> <ins> https://pkg.go.dev/k8s.io/kube-proxy/config/v1alpha1#KubeProxyConfiguration </ins> for kube-proxy official documentation.</p> <pre style="background-color:#fff"><span style="color:#000;font-weight:bold">apiVersion</span>:<span style="color:#bbb"> </span>kubelet.config.k8s.io/v1beta1<span style="color:#bbb"> </span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">kind</span>:<span style="color:#bbb"> </span>KubeletConfiguration<span style="color:#bbb">

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: According to and , so updated the generator and opened a PR which replaces most of string with , but and remain in these files: - Proposed Solution: Maybe we need to check/update the generator again, and then generate references again. Or, if the generator is fine, then we might update those files manually. Page to Update: ,,- ,,- ,meta/v1.Duration,-cacheDuration%20indicates%20the
for kubeadm, the change ~must~ can be done here: but we are in code freeze for 1.24, so let's wait until code freeze is lifted (19th of April) /sig cluster-lifecycle
/triage accepted
/sig node
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/remove-lifecycle stale /assign
/reopen The kubeadm reference is still on its way to be regenerated. The kubelet credential providers one is yet to be fixed.
Reopened this issue. <detailsIn response to : /reopen The kubeadm reference is still on its way to be regenerated. The kubelet credential providers one is yet to be fixed. Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
But I didn't find the link in this file . ,meta/v1.Duration,-cacheDuration%20indicates%20the page points to There are the only links that still exist in this directory : // For semantics around ctx use and closing/ending streaming RPCs, please refer to for example (Code generated by protoc-gen-gogo.

DO NOT EDIT.) If these links need to be updated, they need to be updated in or repository. This part of the update should be beyond the scope of Kubernetes.