This message was deleted.

@nice-horse-9611 I noticed you’ve responded to couple of times on questions related to Harvester / Kube-OVN in this harvester channel. Could you please take a look at my question above when you get a chance? Thanks! 🙏

@witty-musician-14961 1. Yes we support pure underlay but our docs explicitly does not specify it.But we will include the details for v1.8.0. I have tested this and it works. You can use kubectl to apply the resources for now. https://github.com/harvester/harvester/issues/7834#issuecomment-2864671149 2. We do not have an issue created for pure underlay but I could create one and provide documentation. (We do not need any explicit code changes (upstream functionality should work as it is) except for UI changes) 3. I have not tested this combo VMs using pure underlay (routable IPs no encapsulation) + ovn acls. But my assumption is, it should work as any traffic forwarded via the ovs bridge hits the ovn acl rules. I will create a task/test it and document it. Hope this clarifies all your questions.

@nice-horse-9611 Thanks for the detailed steps on ProviderNetwork/VLAN/Subnet setup for underlay VMs. I have a few follow-up questions to clarify our use case: 1. DHCP support – For ProviderNetwork/VLAN subnets, does KubeOVN provide built-in DHCP for VMs, or do we need an external DHCP server? 2. Multiple VLANs/Subnets – Can multiple VLANs/Subnets share the same ProviderNetwork interface? If so, will OVN ACLs/network policies still work independently per subnet? 3. UI support in v1.8 – Can we expect ProviderNetwork/VLAN creation and subnet assignment to appear in the Harvester UI in v1.8, or will it still require CLI/manifest configuration? Thanks for your guidance , this will help us plan our deployment and testing strategy.

@witty-musician-14961 1.For any overlay VMs, kubeovn provides either an IPAM or inbuilt DHCP. (to use the inbuilt DHCP, dhcp has to be enabled explicitly on each subnet ) 2.Multiple Vlans can map to a provider network but subnet to vlan will be 1:1 mapping as each external subnet need to specify a subnet CIDR range which is unique to a vlan. 3. For v1.8.0, you will need to use CLI/kubectl on the kubeovn provider network, vlan resources.The UI task for this is planned for v1.9.0

Thank you, i will test in our env . We are running 1.7.0. I will follow the steps you provided and update you.

@witty-musician-14961 please check my comments in the issue, Thanks

@nice-horse-9611 Thank you for the comment, i have tested as you said hit some roadblocks, i have added new comment. Please check https://github.com/harvester/harvester/issues/10154#issuecomment-4346099158