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
In a shared build environment, we provision build vms on a centralized server to manage multiple pods using snaps-boot. The build vm has a floating ip, as well as access to the management network; however, the managed nodes would try to reach the build vm's floating ip via their public network. We should add an option to add a route to the managed nodes to communicate with the build vm via a specific NIC (e.g., the NIC on the management network instead of the NIC on the public network by default.)
The text was updated successfully, but these errors were encountered:
In a shared build environment, we provision build vms on a centralized server to manage multiple pods using snaps-boot. The build vm has a floating ip, as well as access to the management network; however, the managed nodes would try to reach the build vm's floating ip via their public network. We should add an option to add a route to the managed nodes to communicate with the build vm via a specific NIC (e.g., the NIC on the management network instead of the NIC on the public network by default.)
The text was updated successfully, but these errors were encountered: