github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-09-06 03:33:26 +00:00
Code Issues Projects Releases Wiki Activity

minor docs/error msg cleanup

Browse Source
This commit is contained in:
Amy Unruh
2014-08-06 09:57:00 -07:00
parent aa3ac324bc
commit f9bbddf892
5 changed files with 23 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -55,7 +55,8 @@ cluster/kubecfg.sh rm myNginx
### Running a container (more complete version)
Assuming you've run `hack/dev-build-and-up.sh` and `hack/build-go.sh`:
Assuming you've run `hack/dev-build-and-up.sh` and `hack/build-go.sh`, you
can create a pod like this:
```
@@ -99,6 +100,18 @@ Where pod.json contains something like:
}
```
You can see your cluster's pods:
```
cluster/kubecfg.sh list pods
```
and delete the pod you just created:
```
cluster/kubecfg.sh delete pods/php
```
Look in `api/examples/` for more examples
### Tearing down the cluster

5
docs/getting-started-guides/vagrant.md
View File

@@ -132,6 +132,7 @@ hack/e2e-test.sh
If this is your first time creating the cluster, the kubelet on each minion schedules a number of docker pull requests to fetch prerequisite images. This can take some time and as a result may delay your initial pod getting provisioned.
#### I changed Kubernetes code, but its not running!
#### I changed Kubernetes code, but it's not running!
Are you sure there was no build error? After running $ vagrant provision, scroll up and ensure that each Salt state was completed successfully on each box in the cluster. Its very likely you see a build error due to an error in your source files!
Are you sure there was no build error? After running $ vagrant provision, scroll up and ensure that each Salt state was completed successfully on each box in the cluster.
It's very likely you see a build error due to an error in your source files!