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/access-application-cluster/connecting-frontend-backend.md
+3 -3
View File
@@ -51,7 +51,7 @@ file for the backend Deployment:
Create the backend Deployment:
```
kubectl create -f http://k8s.io/docs/tasks/access-application-cluster/hello.yaml
kubectl create -f https://k8s.io/docs/tasks/access-application-cluster/hello.yaml
```
View information about the backend Deployment:
@@ -97,7 +97,7 @@ that have the labels `app: hello` and `tier: backend`.
Create the `hello` Service:
```
kubectl create -f http://k8s.io/docs/tasks/access-application-cluster/hello-service.yaml
kubectl create -f https://k8s.io/docs/tasks/access-application-cluster/hello-service.yaml
```
At this point, you have a backend Deployment running, and you have a
@@ -124,7 +124,7 @@ the Service uses the default load balancer of your cloud provider.
Create the frontend Deployment and Service:
```
kubectl create -f http://k8s.io/docs/tasks/access-application-cluster/frontend.yaml
kubectl create -f https://k8s.io/docs/tasks/access-application-cluster/frontend.yaml
```
The output verifies that both resources were created: