deprecation of DynamicKubeletConfig feature flag

content/en/docs/tasks/administer-cluster/kubelet-config-file.md

@@ -38,9 +38,6 @@ In the example, the Kubelet is configured to evict Pods when available memory dr
 All other Kubelet configuration values are left at their built-in defaults, unless overridden
 by flags. Command line flags which target the same value as a config file will override that value.
 
-For a trick to generate a configuration file from a live node, see
-[Reconfigure a Node's Kubelet in a Live Cluster](/docs/tasks/administer-cluster/reconfigure-kubelet).
-
 ## Start a Kubelet process configured via the config file
 
 {{< note >}}
@@ -65,12 +62,6 @@ In the above example, this version is `kubelet.config.k8s.io/v1beta1`.
 
 <!-- discussion -->
 
-## Relationship to Dynamic Kubelet Config
-
-If you are using the [Dynamic Kubelet Configuration](/docs/tasks/administer-cluster/reconfigure-kubelet)
-feature, the combination of configuration provided via `--config` and any flags which override these values
-is considered the default "last known good" configuration by the automatic rollback mechanism.
-
 ## {{% heading "whatsnext" %}}
 
 - Learn more about kubelet configuration by checking the

content/en/docs/tasks/administer-cluster/reconfigure-kubelet.md

@@ -8,7 +8,14 @@ min-kubernetes-server-version: v1.11
 ---
 
 <!-- overview -->
-{{< feature-state for_k8s_version="v1.11" state="beta" >}}
+{{< feature-state for_k8s_version="v1.22" state="deprecated" >}}
+
+{{< caution >}}
+[Dynamic Kubelet Configuration](https://github.com/kubernetes/enhancements/issues/281)
+feature is deprecated and should not be used.
+Please switch to alternative means distributing configuration to the Nodes of your cluster.
+{{< /caution >}}
+
 
 [Dynamic Kubelet Configuration](https://github.com/kubernetes/enhancements/issues/281)
 allows you to change the configuration of each