Remove InitialResources from admission controllers

The feature (was experimental) is dropped in 1.11.

xref: kubernetes/kubernetes#58784

docs/admin/admission-controllers.md

@@ -322,17 +322,6 @@ The admission controller determines the initializers of a resource based on the
 metadata of the resource to be created.
 For more information, please check [Dynamic Admission Control](/docs/admin/extensible-admission-controllers.md).
 
-### InitialResources (experimental)
-
-This admission controller observes pod creation requests. If a container omits compute resource requests and limits,
-then the admission controller auto-populates a compute resource request based on historical usage of containers running the same image.
-If there is not enough data to make a decision the Request is left unchanged.
-When the admission controller sets a compute resource request, it does this by *annotating* 
-the pod spec rather than mutating the `container.resources` fields.
-The annotations added contain the information on what compute resources were auto-populated.
-
-See the [InitialResources proposal](https://git.k8s.io/community/contributors/design-proposals/autoscaling/initial-resources.md) for more details.
-
 ### LimitPodHardAntiAffinityTopology
 
 This admission controller denies any pod that defines `AntiAffinity` topology key other than