Flag names changed (s/admission-control/enable-admission-plugins); disable-admissions-plugin entry added; removed reference to admission controller/plugins requiring set order (for v1.10), redundant example enabling specific plugin, and redundant version-specific info (#7449)

docs/concepts/configuration/pod-priority-preemption.md

@@ -45,7 +45,7 @@ Also enable scheduling.k8s.io/v1alpha1 API and Priority [admission controller](/
 
 
 ```
---runtime-config=scheduling.k8s.io/v1alpha1=true --admission-control=Controller-Foo,Controller-Bar,...,Priority
+--runtime-config=scheduling.k8s.io/v1alpha1=true --enable-admission-plugins=Controller-Foo,Controller-Bar,...,Priority
 ```
 
 After the feature is enabled, you can create [PriorityClasses](#priorityclass)

docs/concepts/policy/resource-quotas.md

@@ -42,8 +42,8 @@ Neither contention nor changes to quota will affect already created resources.
 
 ## Enabling Resource Quota
 
-Resource quota support is enabled by default for many Kubernetes distributions.  It is
-enabled when the apiserver `--admission-control=` flag has `ResourceQuota` as
+Resource Quota support is enabled by default for many Kubernetes distributions.  It is
+enabled when the apiserver `--enable-admission-plugins=` flag has `ResourceQuota` as
 one of its arguments.
 
 A resource quota is enforced in a particular namespace when there is a

docs/concepts/storage/persistent-volumes.md

@@ -54,7 +54,7 @@ dynamic provisioning for themselves.
 To enable dynamic storage provisioning based on storage class, the cluster administrator
 needs to enable the `DefaultStorageClass` [admission controller](/docs/admin/admission-controllers/#defaultstorageclass)
 on the API server. This can be done, for example, by ensuring that `DefaultStorageClass` is
-among the comma-delimited, ordered list of values for the `--admission-control` flag of
+among the comma-delimited, ordered list of values for the `--enable-admission-plugins` flag of
 the API server component. For more information on API server command line flags,
 please check [kube-apiserver](/docs/admin/kube-apiserver/) documentation.
 

docs/concepts/workloads/pods/podpreset.md

@@ -68,7 +68,7 @@ In order to use Pod Presets in your cluster you must ensure the following:
     example, this can be done by including `settings.k8s.io/v1alpha1=true` in
     the `--runtime-config` option for the API server. 
 1.  You have enabled the admission controller `PodPreset`. One way to doing this
-    is to include `PodPreset` in the `--admission-control` option value specified
+    is to include `PodPreset` in the `--enable-admission-plugins` option value specified
     for the API server.
 1.  You have defined your Pod Presets by creating `PodPreset` objects in the
     namespace you will use.