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

Merge pull request #3149 from adimania/master 

"kind" is needed to start the pod
pull/6/head
Joe Beda 2014-12-29 09:49:01 -08:00
parent 6c1203bdb8 f86af137e0
commit 75085279eb
2 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/getting-started-guides/fedora/fedora_manual_config.md
View File

@ -128,6 +128,8 @@ done
``` ```
kubectl get minions kubectl get minions
NAME LABELS
fed-minion <none>
``` ```
**The cluster should be running! Launch a test pod.** **The cluster should be running! Launch a test pod.**

3
examples/walkthrough/README.md
View File

@ -11,6 +11,7 @@ Trivially, a single container might be a pod. For example, you can express a si
```yaml ```yaml
apiVersion: v1beta1 apiVersion: v1beta1
kind: Pod
id: www id: www
desiredState: desiredState:
manifest: manifest:
@ -31,6 +32,7 @@ Now that's great for a static web server, but what about persistent storage? We
```yaml ```yaml
apiVersion: v1beta1 apiVersion: v1beta1
kind: Pod
id: storage id: storage
desiredState: desiredState:
manifest: manifest:
@ -88,6 +90,7 @@ However, often you want to have two different containers that work together. An
```yaml ```yaml
apiVersion: v1beta1 apiVersion: v1beta1
kind: Pod
id: www id: www
desiredState: desiredState:
manifest: manifest: