harvester · rrajendran17 · Jul 15, 2026 · Jul 17, 2026 · Jul 17, 2026 · Jul 17, 2026
@@ -95,11 +95,13 @@ When setting up a pure underlay, the overlay network must use the following conf
 
 For descriptions of settings that you must configure, see [Subnet Settings](./kubeovn-vpc.md#subnet-settings).
 
-![](/img/subnetexternal.png)
+![](/img/subnetdhcp.png)
 
 :::info important
 
 When setting up a pure underlay, you must specify the name of the VLAN network that is mapped to the provider network.
+If using this as external network for the `VPC NAT Gateway`, then make sure to enable DHCP and set `dns_server=8.8.8.8` and `natOutgoing` as `true`.
+This will make sure to install default route and resolve dns on the VMs which are using these subnets.
 
 :::
 

@@ -0,0 +1,79 @@
+---
+sidebar_position: 11
+sidebar_label: Guest Cluster using Overlay Network
+title: "Guest Cluster using Overlay Network"
-title: "Guest Cluster using Overlay Network"
+title: "Guest Cluster Provisioning Using Underlay and Overlay Networks"
-title: "Guest Cluster using Overlay Network"
+title: "Guest Cluster Provisioning Using Underlay and Overlay Networks"
+keywords:
+  - Harvester
+  - Rancher
+  - KubeOVN
+---
+
+<head>
+  <link rel="canonical" href="https://docs.harvesterhci.io/v1.9/rancher/guest-cluster-overlay-network"/>
+</head>
+
+## Provisioning Downstream Kubernetes Clusters on Harvester Using Rancher and Kube-OVN Networking
+
+### Introduction
+
+Rancher provides centralized management for Kubernetes clusters across multiple environments. When integrated with Harvester, Rancher can provision guest Kubernetes clusters directly on virtual machine infrastructure managed by Harvester.
+
+Using the Harvester Node Driver, Rancher automatically creates virtual machines that serve as control plane and worker nodes. This simplifies cluster deployment and lifecycle management by providing a single interface for infrastructure and Kubernetes operations.
+
+While guest clusters can use traditional virtual machine networking, they can also leverage Kube-OVN overlay or underlay networking to provide a flexible and Kubernetes-native networking model for workloads.
+
+## Guest Cluster Deployment on Underlay Network
+
+Deploying guest clusters on pure underlay networks is functionally similar to using traditional virtual machine VLAN networks, but with the added advantages of Kube-OVN features such as network policies and tenant-isolated VPCs.
+
+For information about setting up the overlay infrastructure, see [Create an underlay network](../networking/kubeovn-pureunderlay.md#underlay-configuration).
+
+## Guest Cluster Deployment on Overlay Network
+
+Deploying guest clusters on overlay networks requires configuring a VPC NAT gateway to provide inbound and outbound connectivity to the virtual machines through DNAT and SNAT.
+
+The key architectural features are as follows:
+
+- Harvester provides the virtual machine infrastructure for the guest cluster's control plane and worker nodes.
+- Rancher provisions and manages the lifecycle of the guest cluster.
+- Kube-OVN provides networking within the guest cluster using overlay tunnels between the guest nodes.
+- Pod communication is encapsulated and transported across the overlay network connecting the guest nodes.
+
+Kube-OVN overlay networking enables guest clusters to manage pod networking independently of the underlying Harvester infrastructure network. This provides the following operational benefits:
+
+- Simplified cluster deployment
+- Reduced dependence on physical network configuration
+- Dynamic cluster scaling without additional VLAN planning
+- Consistent networking model across environments
+
+For information about setting up the overlay infrastructure, see [Create a VPC NAT Gateway](../networking/kubeovn-vpcnatgateway.md#kubeovn-as-secondary-cni).
+
+## Guest Cluster Provisioning
+
+### Importing Harvester Clusters into Rancher
+
+Harvester clusters are imported through Rancher's **Virtualization Management** interface.
+
+The following occur after a Harvester cluster is imported:
+
+- Rancher recognizes the cluster as a Harvester provider.
+- Virtual machine resources become available through Rancher.
+- Harvester can be selected as an infrastructure provider when creating downstream clusters.
+
+For detailed instructions, see [Importing Harvester Cluster](./virtualization-management.md#importing-harvester-cluster).
+
+### Provisioning a Guest Cluster
+
+Rancher uses the Harvester Node Driver to automatically provision the required virtual machines and bootstrap Kubernetes on them.
+
+For detailed instructions, see [Harvester Node Driver](./node/rke2-cluster.md).
+
+:::info important
+
+In the **Networks** section of the cluster creation screen, you must specify the correct underlay or overlay network.
+
+:::
+
+![](/img/v1.9/rancher/gc-overlayvmnetwork.png)
+
+![](/img/v1.9/rancher/gc-overlayvm.png)