https://rancher.com/ logo
Join SlackCommunities
Powered by
This message was deleted.
# harvester
a
This message was deleted.
b
Hi @red-king-19196, sorry to ping you again. Do you have any idea about this? Thank you.
a
We have a discussing in a earlier thread where we discussed this
👍 1
👀 1
a
Unfortunately, from VM type LB, it does not support none-management network.
The VM can only be based on mgmt network to have LB working.
a
I have a thread with Zespre Chang, but I have let him know that for big enterprise customers, this is a big security risk, to have a LB in the same network as physical nodes. though for my homelab its fine.
a
https://docs.harvesterhci.io/v1.3/networking/loadbalancer#limitations
Copy code
Access Restriction: The VM LB address is exposed only within the same network as the Harvester hosts. To access the LB from outside the network, you must provide a route from outside to the LB address.
a
I couldnt delete this post in this channel.
I see this feature has been moved to 1.5.0 milestone
a
It is technical limitation. The Harvester LB is currently on-top of k8s LB, it can only work on k8s network.
For none-mgmt network, we are working on solutions.
a
True, though you guys made some hackish fix for Rancher/Harvester Cloud Provider for guest lb
a
No, no tricky. guest LB is indeed on top of guest k8s LB.
a
I dont say its easy to fix, but as stated in the other bigger thread with Zespre. To get this as a Enterprise ready feature this should be fixed. preferably before 1.5.0.
a
Let me take a look of this huge thread 🙂
a
but yeah we have understood how this is done as is today.
Open in Slack
PreviousNext
Powered by