github/client-go
1
0
Fork 0
mirror of https://github.com/kubernetes/client-go.git synced 2025-09-15 14:48:16 +00:00
Code Issues Projects Releases Wiki Activity

Update some readme.md files in client-go

Browse Source 
Kubernetes-commit: 1c424fddc2a564588fc5b32731cf4c0e52f86ef7
This commit is contained in:
aaa
2019-04-09 06:56:52 -04:00
committed by Kubernetes Publisher
parent ca8df85b17
commit 90da71b8c3
4 changed files with 13 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
examples/in-cluster-client-configuration/README.md
View File

@@ -37,7 +37,7 @@ kubectl create clusterrolebinding default-view --clusterrole=view --serviceaccou
Then, run the image in a Pod with a single instance Deployment:
$ kubectl run --rm -i demo --image=in-cluster --image-pull-policy=Never
kubectl run --rm -i demo --image=in-cluster --image-pull-policy=Never
There are 4 pods in the cluster
There are 4 pods in the cluster

8
examples/leader-election/README.md
View File

@@ -8,14 +8,14 @@ Run the following three commands in separate terminals. Each terminal needs a un
```bash
# first terminal
$ go run *.go -kubeconfig=/my/config -logtostderr=true -id=1
go run *.go -kubeconfig=/my/config -logtostderr=true -id=1
# second terminal
$ go run *.go -kubeconfig=/my/config -logtostderr=true -id=2
go run *.go -kubeconfig=/my/config -logtostderr=true -id=2
# third terminal
$ go run *.go -kubeconfig=/my/config -logtostderr=true -id=3
go run *.go -kubeconfig=/my/config -logtostderr=true -id=3
```
> You can ignore the `-kubeconfig` flag if you are running these commands in the Kubernetes cluster.
Now kill the existing leader. You will see from the terminal outputs that one of the remaining two processes will be elected as the new leader.
Now kill the existing leader. You will see from the terminal outputs that one of the remaining two processes will be elected as the new leader.

2
examples/out-of-cluster-client-configuration/README.md
View File

@@ -22,7 +22,7 @@ Run this application with:
Running this application will use the kubeconfig file and then authenticate to the
cluster, and print the number of pods in the cluster every 10 seconds:
$ ./app
./app
There are 3 pods in the cluster
There are 3 pods in the cluster
There are 3 pods in the cluster