You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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).
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 portThen the RNG app would be accessible from the Linux host by going to the address http://127.0.0.1:30001
The text was updated successfully, but these errors were encountered: