github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #53520 from shun-miyoshi-com/fix_old_name

Browse Source 
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

fix kubemark, juju, and libvirt-coreos README (from minions to nodes)

**What this PR does / why we need it**:
This PR will fix old name(minison) to new name(node) in kubemark README.md.

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #

**Special notes for your reviewer**:

**Release note**:

```release-note
```
This commit is contained in:
Kubernetes Submit Queue 2017-10-17 01:36:33 -07:00 committed by GitHub
commit ebe8421353
3 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
cluster/juju/bundles/README.md
View File

@ -51,7 +51,7 @@ The command above does few things for you:
deployment environment (machine 0). deployment environment (machine 0).
- Deploys the Juju GUI to your environment onto the bootstrap node. - Deploys the Juju GUI to your environment onto the bootstrap node.
- Provisions 4 machines, and deploys the Kubernetes services on top of - Provisions 4 machines, and deploys the Kubernetes services on top of
them (Kubernetes-master, two Kubernetes minions using flannel, and etcd). them (Kubernetes-master, two Kubernetes nodes using flannel, and etcd).
- Orchestrates the relations among the services, and exits. - Orchestrates the relations among the services, and exits.
Now you should have a running Kubernetes. Run `juju status Now you should have a running Kubernetes. Run `juju status
@ -113,9 +113,9 @@ capabilities to the charms.
The master controls the Kubernetes cluster. It manages for the worker The master controls the Kubernetes cluster. It manages for the worker
nodes and provides the primary interface for control by the user. nodes and provides the primary interface for control by the user.
### Kubernetes minion ### Kubernetes node
The minions are the servers that perform the work. Minions must The nodes are the servers that perform the work. Nodes must
communicate with the master and run the workloads that are assigned to communicate with the master and run the workloads that are assigned to
them. them.

2
cluster/libvirt-coreos/README.md
View File

@ -1,7 +1,7 @@
# Kubernetes CoreOS cluster # Kubernetes CoreOS cluster
With this tutorial one creates a Kubernetes CoreOS cluster containing of one With this tutorial one creates a Kubernetes CoreOS cluster containing of one
master and three minions (workers) running on `192.168.10.1`-`192.168.10.4`. master and three nodes (workers) running on `192.168.10.1`-`192.168.10.4`.
For working correctly you need to create the directory addressed as `POOL_PATH` in For working correctly you need to create the directory addressed as `POOL_PATH` in
`util.sh`: `util.sh`:

2
test/kubemark/pre-existing/README.md
View File

@ -4,7 +4,7 @@
- A set of Kubernetes control plane components running in a VM - A set of Kubernetes control plane components running in a VM
**Kubernetes Cluster** **Kubernetes Cluster**
- A real Kubernetes Cluster that has master and minions. The hollow-node pods - A real Kubernetes Cluster that has master and nodes. The hollow-node pods
are run in this cluster, but appear as nodes to the Kubemark Master are run in this cluster, but appear as nodes to the Kubemark Master
## Introduction ## Introduction