-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Some minor cleanups and simplifications to the ansible directions. #5760
Conversation
7f20031
to
884b3f8
Compare
|
||
/usr/bin/kubectl create -f apache.json | ||
|
||
**Testing you're new kube cluster** |
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.
s/you're/your
Some grammatical suggestions. Otherwise lgtm. |
172c8e2
to
dd9eaed
Compare
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
450662a
to
25b99d4
Compare
CLAs look good, thanks! |
okay, fixed. thanks for the fast review. just some minor updates hope this helps folks using ansible. |
``` | ||
|
||
**Tell ansible which user has ssh access (and sudo access to root)** | ||
**Setup ansible access to youre 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.
one more.... since I can't merge until tomorrow anyway, might as well fix this one too.
s/youre/your
c5f4766
to
a5b8ebf
Compare
rebased and added one more detail, about how you need to check the IPs after setup. |
LGTM. Will merge on green. |
Both travis and shippable have failed a few times in a row. I don't see how it could be related to your (documentation) change, but you may have been sync'd to an unstable commit. Could you sync to head and refresh this branch so we get a clean test run before merging? Sorry for the trouble. |
@jayunit100 to pick up the fixes you should sync beyond #5775. |
…nts for ansible setup
a5b8ebf
to
378b1b0
Compare
hmm yes maybe your right, and maybe thats whats caused other pushes of mine to fail.... okay i rebased and pushed |
Thanks, and sorry for the hassle. I'll merge in the morning during merge hours. |
no prob ! thanks for the review. |
Some minor cleanups and simplifications to the ansible directions.
... works fabulously, btw.