whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source 
k8s.io didn't always have https. But, now we do. We should fix this
immediatly.
This commit is contained in:
Brandon Philips
2017-05-17 20:14:09 -07:00
parent 411ecca94d
commit 3b5bdc3f00
25 changed files with 43 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tasks/debug-application-cluster/determine-reason-pod-failure.md
+1 -1
View File
@@ -37,7 +37,7 @@ the container starts.
1. Create a Pod based on the YAML configuration file:
kubectl create -f http://k8s.io/docs/tasks/debug-application-cluster/termination.yaml
kubectl create -f https://k8s.io/docs/tasks/debug-application-cluster/termination.yaml
In the YAML file, in the `cmd` and `args` fields, you can see that the
container sleeps for 10 seconds and then writes "Sleep expired" to
docs/tasks/debug-application-cluster/logging-stackdriver.md
+2 -2
View File
@@ -125,7 +125,7 @@ that writes out the value of a counter and the date once per
second, and runs indefinitely. Let's create this pod in the default namespace.
```shell
kubectl create -f http://k8s.io/docs/tasks/debug-application-cluster/counter-pod.yaml
kubectl create -f https://k8s.io/docs/tasks/debug-application-cluster/counter-pod.yaml
```
You can observe the running pod:
@@ -162,7 +162,7 @@ pod "counter" deleted
and then recreating it:
```shell
$ kubectl create -f http://k8s.io/docs/tasks/debug-application-cluster/counter-pod.yaml
$ kubectl create -f https://k8s.io/docs/tasks/debug-application-cluster/counter-pod.yaml
pod "counter" created
```