Move ReplicationController sample YAML to examples

In aid of #12740

content/en/docs/tasks/run-application/rolling-update-replication-controller.md

@@ -91,9 +91,9 @@ kubectl rolling-updatea NAME NEW_NAME --image=IMAGE:TAG
 The `--image` flag is only supported for single-container pods. Specifying
 `--image` with multi-container pods returns an error.
 
-If no `NEW_NAME` is specified, a new replication controller is created with
-a temporary name. Once the rollout is complete, the old controller is deleted,
-and the new controller is updated to use the original name.
+If you didn't specify a new name, this creates a new replication controller
+with a temporary name. Once the rollout is complete, the old controller is
+deleted, and the new controller is updated to use the original name.
 
 The update will fail if `IMAGE:TAG` is identical to the
 current value. For this reason, we recommend the use of versioned tags as
@@ -155,24 +155,7 @@ from the [`kubectl` reference](/docs/reference/generated/kubectl/kubectl-command
 
 Let's say you were running version 1.7.9 of nginx:
 
-```yaml
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: my-nginx
-spec:
-  replicas: 5
-  template:
-    metadata:
-      labels:
-        app: nginx
-    spec:
-      containers:
-      - name: nginx
-        image: nginx:1.7.9
-        ports:
-        - containerPort: 80
-```
+{{< codenew file="controllers/replication-nginx-1.7.9.yaml" >}}
 
 To update to version 1.9.1, you can use [`kubectl rolling-update --image`](https://git.k8s.io/community/contributors/design-proposals/cli/simple-rolling-update.md) to specify the new image:
 
@@ -230,34 +213,13 @@ This is one example where the immutability of containers is a huge asset.
 
 If you need to update more than just the image (e.g., command arguments, environment variables), you can create a new replication controller, with a new name and distinguishing label value, such as:
 
-```yaml
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: my-nginx-v4
-spec:
-  replicas: 5
-  selector:
-    app: nginx
-    deployment: v4
-  template:
-    metadata:
-      labels:
-        app: nginx
-        deployment: v4
-    spec:
-      containers:
-      - name: nginx
-        image: nginx:1.9.2
-        args: ["nginx", "-T"]
-        ports:
-        - containerPort: 80
-```
+{{< codenew file="controllers/replication-nginx-1.9.2.yaml" >}}
 
 and roll it out:
 
 ```shell
-kubectl rolling-update my-nginx -f ./nginx-rc.yaml
+# Assuming you named the file "my-nginx.yaml"
+kubectl rolling-update my-nginx -f ./my-nginx.yaml
 ```
 ```
 Created my-nginx-v4

content/en/examples/controllers/replication-nginx-1.7.9.yaml

@@ -0,0 +1,16 @@
+apiVersion: v1
+kind: ReplicationController
+metadata:
+  name: my-nginx
+spec:
+  replicas: 5
+  template:
+    metadata:
+      labels:
+        app: nginx
+    spec:
+      containers:
+      - name: nginx
+        image: nginx:1.7.9
+        ports:
+        - containerPort: 80

content/en/examples/controllers/replication-nginx-1.9.2.yaml

@@ -0,0 +1,21 @@
+apiVersion: v1
+kind: ReplicationController
+metadata:
+  name: my-nginx-v4
+spec:
+  replicas: 5
+  selector:
+    app: nginx
+    deployment: v4
+  template:
+    metadata:
+      labels:
+        app: nginx
+        deployment: v4
+    spec:
+      containers:
+      - name: nginx
+        image: nginx:1.9.2
+        args: ["nginx", "-T"]
+        ports:
+        - containerPort: 80