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

Ch 18 - Vagrant labs - missing Linux host specific instructions #15

Open
lalanikarim opened this issue May 28, 2021 · 0 comments
Open

Comments

@lalanikarim
Copy link

On a Linux host, the hosted apps running on the cluster are not accessible from the host machine (probably due to the network being private).

# Page 482 of the ebook states
The app is running and the NodePort Service means all nodes are listening on
port 30000, including the control plane node. If you browse to any node’s IP address,
you’ll see the APOD app. Your request is directed to the web Pod on the standard
node, and it makes an API call, which could be directed to a Pod on either node.

On Linux host, since the VMs are setup in a private network, they are not accessible via the Node IP address from the host machine. Instead, the NodePort port number has to be forwarded to the VM nodes in the Vagrantfile (vagrant reload kiamol-control command is needed for changes to take effect) and then the app is available via IP address of the Linux Host on that specified port

control.vm.network "forwarded_port", guest: 30000, host: 30000
control.vm.network "forwarded_port", guest: 30001, host: 30001

Then the RNG app would be accessible from the Linux host by going to the address http://127.0.0.1:30001

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant