Merge pull request #22054 from soltysh/kubectl_run_updates

Update kubectl run from docs where necessary

content/en/docs/concepts/configuration/overview.md

@@ -103,7 +103,7 @@ The caching semantics of the underlying image provider make even `imagePullPolic
 
 - Use label selectors for `get` and `delete` operations instead of specific object names. See the sections on [label selectors](/docs/concepts/overview/working-with-objects/labels/#label-selectors) and [using labels effectively](/docs/concepts/cluster-administration/manage-deployment/#using-labels-effectively).
 
-- Use `kubectl run` and `kubectl expose` to quickly create single-container Deployments and Services. See [Use a Service to Access an Application in a Cluster](/docs/tasks/access-application-cluster/service-access-application-cluster/) for an example.
+- Use `kubectl create deployment` and `kubectl expose` to quickly create single-container Deployments and Services. See [Use a Service to Access an Application in a Cluster](/docs/tasks/access-application-cluster/service-access-application-cluster/) for an example.
 
 
 

content/en/docs/concepts/overview/working-with-objects/object-management.md

@@ -40,12 +40,6 @@ objects, it provides no history of previous configurations.
 
 Run an instance of the nginx container by creating a Deployment object:
 
-```sh
-kubectl run nginx --image nginx
-```
-
-Do the same thing using a different syntax:
-
 ```sh
 kubectl create deployment nginx --image nginx
 ```

content/en/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases.md

@@ -23,7 +23,7 @@ Modification not using HostAliases is not suggested because the file is managed
 Start an Nginx Pod which is assigned a Pod IP:
 
 ```shell
-kubectl run nginx --image nginx --generator=run-pod/v1
+kubectl run nginx --image nginx
 ```
 
 ```
@@ -64,7 +64,7 @@ By default, the `hosts` file only includes IPv4 and IPv6 boilerplates like
 ## Adding additional entries with hostAliases
 
 In addition to the default boilerplate, you can add additional entries to the
-`hosts` file.  
+`hosts` file.
 For example: to resolve `foo.local`, `bar.local` to `127.0.0.1` and `foo.remote`,
 `bar.remote` to `10.1.2.3`, you can configure HostAliases for a Pod under
 `.spec.hostAliases`: