*: don't create -f from http endpoints!

k8s.io didn't always have https. But, now we do. We should fix this
immediatly.

docs/tasks/configure-pod-container/assign-cpu-ram-container.md

@@ -44,7 +44,7 @@ for the `Pod`:
 
 1. Create a Pod based on the YAML configuration file:
 
-        kubectl create -f http://k8s.io/docs/tasks/configure-pod-container/cpu-ram.yaml
+        kubectl create -f https://k8s.io/docs/tasks/configure-pod-container/cpu-ram.yaml
 
 1. Display information about the pod:
 

docs/tasks/configure-pod-container/assign-pods-nodes.md

@@ -63,7 +63,7 @@ a `disktype=ssd` label.
 1. Use the configuration file to create a pod that will get scheduled on your
    chosen node:
 
-        kubectl create -f http://k8s.io/docs/tasks/configure-pod-container/pod.yaml
+        kubectl create -f https://k8s.io/docs/tasks/configure-pod-container/pod.yaml
 
 1. Verify that the pod is running on your chosen node:
 

docs/tasks/configure-pod-container/attach-handler-lifecycle-event.md

@@ -36,7 +36,7 @@ nginx gracefully. This is helpful if the Container is being terminated because o
 
 Create the Pod:
 
-    kubectl create -f http://k8s.io/docs/tasks/configure-pod-container/lifecycle-events.yaml
+    kubectl create -f https://k8s.io/docs/tasks/configure-pod-container/lifecycle-events.yaml
 
 Verify that the Container in the Pod is running:
 

docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md

@@ -63,7 +63,7 @@ code. After 30 seconds, `cat /tmp/healthy` returns a failure code.
 Create the Pod:
 
 ```shell
-kubectl create -f http://k8s.io/docs/tasks/configure-pod-container/exec-liveness.yaml
+kubectl create -f https://k8s.io/docs/tasks/configure-pod-container/exec-liveness.yaml
 ```
 
 Within 30 seconds, view the Pod events:
@@ -164,7 +164,7 @@ checks will fail, and the kubelet will kill and restart the Container.
 To try the HTTP liveness check, create a Pod:
 
 ```shell
-kubectl create -f http://k8s.io/docs/tasks/configure-pod-container/http-liveness.yaml
+kubectl create -f https://k8s.io/docs/tasks/configure-pod-container/http-liveness.yaml
 ```
 
 After 10 seconds, view Pod events to verify that liveness probes have failed and

docs/tasks/configure-pod-container/configure-persistent-volume-storage.md

@@ -72,7 +72,7 @@ read-write by a single Node.
 
 Create the PersistentVolume:
 
-    kubectl create -f http://k8s.io/docs/tasks/configure-pod-container/task-pv-volume.yaml
+    kubectl create -f https://k8s.io/docs/tasks/configure-pod-container/task-pv-volume.yaml
 
 View information about the PersistentVolume:
 
@@ -98,7 +98,7 @@ Here is the configuration file for the PersistentVolumeClaim:
 
 Create the PersistentVolumeClaim:
 
-    kubectl create -f http://k8s.io/docs/tasks/configure-pod-container/task-pv-claim.yaml
+    kubectl create -f https://k8s.io/docs/tasks/configure-pod-container/task-pv-claim.yaml
 
 After you create the PersistentVolumeClaim, the Kubernetes control plane looks
 for a PersistentVolume that satisfies the claim's requirements. If the control
@@ -138,7 +138,7 @@ is a volume.
 
 Create the Pod:
 
-    kubectl create -f http://k8s.io/docs/tasks/configure-pod-container/task-pv-pod.yaml
+    kubectl create -f https://k8s.io/docs/tasks/configure-pod-container/task-pv-pod.yaml
 
 Verify that the Container in the Pod is running;
 

docs/tasks/configure-pod-container/configure-pod-initialization.md

@@ -41,7 +41,7 @@ of the nginx server.
 
 Create the Pod:
 
-    kubectl create -f http://k8s.io/docs/tasks/configure-pod-container/init-containers.yaml
+    kubectl create -f https://k8s.io/docs/tasks/configure-pod-container/init-containers.yaml
 
 Verify that the nginx container is running:
 

docs/tasks/configure-pod-container/configure-volume-storage.md

@@ -35,7 +35,7 @@ restarts. Here is the configuration file for the Pod:
 
 1. Create the Pod:
 
-        kubectl create -f http://k8s.io/docs/tasks/configure-pod-container/pod-redis.yaml
+        kubectl create -f https://k8s.io/docs/tasks/configure-pod-container/pod-redis.yaml
 
 1. Verify that the Pod's Container is running, and then watch for changes to
 the Pod: