-
Notifications
You must be signed in to change notification settings - Fork 87
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 NAT and make it working for Terraform and Vagrant #41
Conversation
setup.sh
Outdated
) | ||
|
||
do_setup() ( | ||
o_setup() ( |
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.
This does not look intentional.
Yep I think looks good, noting the same thing that @gauravgahlot mentioned :D. |
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.
approved, assuming you fix what @gauravgahlot mentioned
Commit b504810 introduced a NAT to make worker capable of reaching the public internet via the provisioner. But it also introduced a bug, it only works for the Vagrant setup as Manny pointed out: #33 (comment) This is an attempt to fix it Signed-off-by: Gianluca Arbezzano <[email protected]>
Commit b504810 introduced a NAT to make worker capable of reaching the public internet via the provisioner. But it also introduced a bug, it only works for the Vagrant setup as Manny pointed out: tinkerbell#33 (comment) This is an attempt to fix it @mmlb I would like to avoid additional conditions as part of the setup.sh, we have already too many of them and they are not even easy to dsicover. We have different entrypoint for those environment let's use them.
Commit b504810 introduced a NAT to make worker capable of reaching the
public internet via the provisioner.
But it also introduced a bug, it only works for the Vagrant setup as
Manny pointed out:
#33 (comment)
This is an attempt to fix it
@mmlb I would like to avoid additional conditions as part of the
setup.sh, we have already too many of them and they are not even easy to
dsicover. We have different entrypoint for those environment let's use them.