github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Modify nginx port to avoid collision with api server

pull/6/head
Prashanth Balasubramanian 2015-02-10 16:19:16 -08:00
parent c2b0632be4
commit ec298733c7
2 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
api/examples/pod.json
View File

@ -11,7 +11,7 @@
"image": "dockerfile/nginx",
"ports": [{
"containerPort": 80,
"hostPort": 8080
"hostPort": 8081
}],
"livenessProbe": {
"enabled": true,
@ -19,7 +19,7 @@
"initialDelaySeconds": 30,
"httpGet": {
"path": "/index.html",
"port": "8080"
"port": "8081"
}
}
}]

7
docs/getting-started-guides/gce.md
View File

@ -96,7 +96,7 @@ Where pod.json contains something like:
"image": "dockerfile/nginx",
"ports": [{
"containerPort": 80,
"hostPort": 8080
"hostPort": 8081
}],
"livenessProbe": {
"enabled": true,
@ -104,7 +104,7 @@ Where pod.json contains something like:
"initialDelaySeconds": 30,
"httpGet": {
"path": "/index.html",
"port": "8080"
"port": "8081"
}
}
}]
@ -128,6 +128,9 @@ and delete the pod you just created:
cluster/kubectl.sh delete pods php
```
Since this pod is scheduled on a minion running in GCE, you will have to enable incoming tcp traffic via the port specified in the
pod manifest before you see the nginx welcome page. After doing so, it should be visible at http://<external ip of minion running nginx>:<port from manifest>.
Look in `examples/` for more examples
### Tearing down the cluster