Skip to content
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

Fix Vagrant node registration and kube-push #8865

Merged
merged 1 commit into from
May 27, 2015

Conversation

derekwaynecarr
Copy link
Member

This makes the following fixes to the Vagrant setup:

  1. Fix node kubelet registration. Kubelet uses cloud-provider now, and the vagrant provider was backed by the salt-api. The salt-api was previously only available on the master over 127.0.0.1. To make it accessible to the nodes, had to listen on the MASTER_IP, and update the cloud provider code to reference by host name.
  2. Fix kube-push as recent versions of salt do not support --show-timeout flag

These changes make the cluster come up successfully.

@thockin thockin added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 27, 2015
@thockin thockin self-assigned this May 27, 2015
thockin added a commit that referenced this pull request May 27, 2015
Fix Vagrant node registration and kube-push
@thockin thockin merged commit b74786c into kubernetes:master May 27, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm "Looks good to me", indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants