-
Notifications
You must be signed in to change notification settings - Fork 40.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change 'minion' to 'node' in docs #11130
Conversation
GCE e2e build/test passed for commit bcbd0638d1e9dbe4cf5aef1472246d9e9794aed5. |
#10843 is also making a similar change |
@@ -13,7 +13,7 @@ Running kubernetes with Vagrant (and VirtualBox) is an easy way to run/test/deve | |||
|
|||
### Setup | |||
|
|||
By default, the Vagrant setup will create a single kubernetes-master and 1 kubernetes-minion. Each VM will take 1 GB, so make sure you have at least 2GB to 4GB of free memory (plus appropriate free disk space). To start your local cluster, open a shell and run: | |||
By default, the Vagrant setup will create a single kubernetes-master and 1 node (kubernetes-minion). Each VM will take 1 GB, so make sure you have at least 2GB to 4GB of free memory (plus appropriate free disk space). To start your local cluster, open a shell and run: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
kubernetes-minon/kubernetes-node?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replace first sentence with:
By default, the Vagrant setup will create a single master node (called kubernetes-master) and 1 node (called kubernetes-minion-1).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
next push
Few comments, but first pass looks good to me. |
@@ -58,7 +59,7 @@ We will set the kube_ip_addr to '10.254.0.[1-3]', for now. The reason we do thi | |||
[etcd] | |||
192.168.121.205 | |||
|
|||
[minions] | |||
[nodes] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure this change is safe.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I doubt this can be changed without also updating https://github.com/eparis/kubernetes-ansible
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oops, good catch
new push is up |
LGTM other than the one typo that was introduced |
GCE e2e build/test passed for commit 918bdd3a11144091b58b4ad2db34cce28959d491. |
LGTM |
GCE e2e build/test passed for commit 40a4e6a66b724306fba8554195162dd363b01df1. |
GCE e2e build/test failed for commit 96ceb7ea2e34ca79de6e69d192d6dcd2d8777de7. |
Got unresolved merge conflicts |
Merge resolved. Watching shippable. So tired of saying that. |
LGTM |
GCE e2e build/test passed for commit 494d0ff39cf8a820e467fa492cb2a1020740d251. |
1/2 shippable fails the same way every time:
But it passes for me manually. |
Merge and cross fingers. |
Change 'minion' to 'node' in docs
GCE e2e build/test failed for commit 5cf5445. |
It's less than I wanted to get in, but better than nothing.