rancher/multus-cni
1
0
Fork 0
forked from github/multus-cni
Code Issues Pull Requests Projects Releases Wiki Activity

Remove referecne to minions

Browse Source 
The term "minion" was changed to "node" in 2014,  The discussion and eventual deprcation is documented on 
https://github.com/kubernetes/kubernetes/issues/1111

"A node is a worker machine in Kubernetes, previously known as a minion." - https://kubernetes.io/docs/concepts/architecture/nodes/

updating the documentation to reflect correct terminology
This commit is contained in:
Dave
2018-02-28 11:58:58 +00:00
committed by GitHub
parent 1ea64694f2
commit 6f6a4c20e6
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@@ -334,10 +334,10 @@ sriov-vlanid-l2enable-conf Network.v1.kubernetes.com
sriov-conf Network.v1.kubernetes.com sriov-conf Network.v1.kubernetes.com
``` ```
### Configuring Multus to use the kubeconfig ### Configuring Multus to use the kubeconfig
1. Create Multus CNI configuration file /etc/cni/net.d/multus-cni.conf with below content in minions. Use only the absolute path to point to the kubeconfig file (it may change depending upon your cluster env) and make sure all CNI binary files are in `\opt\cni\bin` dir 1. Create Multus CNI configuration file /etc/cni/net.d/multus-cni.conf with below content on the nodes. Use only the absolute path to point to the kubeconfig file (it may change depending upon your cluster env) and make sure all CNI binary files are in `\opt\cni\bin` dir
``` ```
{ {
"name": "minion-cni-network", "name": "node-cni-network",
"type": "multus", "type": "multus",
"kubeconfig": "/etc/kubernetes/node-kubeconfig.yaml" "kubeconfig": "/etc/kubernetes/node-kubeconfig.yaml"
} }
@@ -350,7 +350,7 @@ sriov-conf Network.v1.kubernetes.com
1. Many user want default networking feature along with Network object. Refer [#14](https://github.com/Intel-Corp/multus-cni/issues/14) & [#17](https://github.com/Intel-Corp/multus-cni/issues/17) issues for more information. In this following config, Weave act as the default network in the absence of network field in the pod metadata annotation. 1. Many user want default networking feature along with Network object. Refer [#14](https://github.com/Intel-Corp/multus-cni/issues/14) & [#17](https://github.com/Intel-Corp/multus-cni/issues/17) issues for more information. In this following config, Weave act as the default network in the absence of network field in the pod metadata annotation.
``` ```
{ {
"name": "minion-cni-network", "name": "node-cni-network",
"type": "multus", "type": "multus",
"kubeconfig": "/etc/kubernetes/node-kubeconfig.yaml", "kubeconfig": "/etc/kubernetes/node-kubeconfig.yaml",
"delegates": [{ "delegates": [{