harvester · innobead · Dec 11, 2025 · Dec 10, 2025 · Dec 11, 2025 · Dec 11, 2025
diff --git a/docs/advanced/addons.md b/docs/advanced/addons.md
@@ -15,7 +15,7 @@ The following add-ons are available in this version:
 * [harvester-csi-driver-lvm](./addons/lvm-local-storage.md) (Experimental)
 * [harvester-seeder](./addons/seeder.md) (Experimental)
 * [harvester-vm-dhcp-controller](./addons/managed-dhcp.md) (Experimental)
-* [kubeovn-operator](./addons/kubeovn-operator.md)
+* [kubeovn-operator](./addons/kubeovn-operator.md) (Experimental)
 * [nvidia-driver-toolkit](./addons/nvidiadrivertoolkit)
 * [pcidevices-controller](./addons/pcidevices.md)
 * [rancher-logging](../logging/harvester-logging.md)

diff --git a/docs/advanced/addons/kubeovn-operator.md b/docs/advanced/addons/kubeovn-operator.md
@@ -1,7 +1,7 @@
 ---
 sidebar_position: 9
 sidebar_label: Kube-OVN Operator
-title: "Kube-OVN Operator"
+title: "Kube-OVN Operator (Experimental)"
 ---
 
 <head>
@@ -10,6 +10,12 @@ title: "Kube-OVN Operator"
 
 _Available as of v1.6.0_
 
+:::note
+
+**kubeovn-operator** is an *experimental* add-on. For more information about experimental features, see [Feature Labels](../../getting-started/document-conventions.md#feature-labels).
+
+:::
+
 [`kubeovn-operator`](https://github.com/harvester/kubeovn-operator) is used to manage the lifecycle of [Kube-OVN](https://github.com/kubeovn/kube-ovn) as a secondary CNI on underlying Harvester clusters.
 
 ## Enabling `kubeovn-operator`

diff --git a/docs/networking/kubeovn-vm-isolation.md b/docs/networking/kubeovn-vm-isolation.md
@@ -15,6 +15,12 @@ keywords:
   <link rel="canonical" href="https://docs.harvesterhci.io/v1.6/networking/kubeovn-vm-isolation"/>
 </head>
 
+:::note
+
+All features that use Kube-OVN are considered experimental. For more information about experimental features, see [Feature Labels](../getting-started/document-conventions.md#feature-labels).
+
+:::
+
 Isolation between virtual machines is typically achieved using either VLANs (in traditional networks) or virtual switches (in Kube-OVN). If you want to isolate virtual machines within the same virtual switch network, you can use either of the following to achieve the required micro-segmentation:
 
 - Subnet access control lists (ACLs): Apply rules to a subnet used by virtual machines.

diff --git a/docs/networking/kubeovn-vpc.md b/docs/networking/kubeovn-vpc.md
@@ -16,6 +16,12 @@ keywords:
   <link rel="canonical" href="https://docs.harvesterhci.io/v1.6/networking/kubeovn-vpc"/>
 </head> 
 
+:::note
+
+All features that use Kube-OVN are considered experimental. For more information about experimental features, see [Feature Labels](../getting-started/document-conventions.md#feature-labels).
+
+:::
+
 A virtual private cloud (VPC) is a logically isolated network that provides full control over IP addresses, subnets, route tables, firewalls, and gateways within a cloud infrastructure. VPCs allow the secure and scalable deployment of virtualized resources such as compute, storage, and container services.
 
 The following table outlines the key components of a VPC:

diff --git a/versioned_docs/version-v1.6/advanced/addons.md b/versioned_docs/version-v1.6/advanced/addons.md
@@ -15,7 +15,7 @@ The following add-ons are available in this version:
 * [harvester-csi-driver-lvm](./addons/lvm-local-storage.md) (Experimental)
 * [harvester-seeder](./addons/seeder.md) (Experimental)
 * [harvester-vm-dhcp-controller](./addons/managed-dhcp.md) (Experimental)
-* [kubeovn-operator](./addons/kubeovn-operator.md)
+* [kubeovn-operator](./addons/kubeovn-operator.md) (Experimental)
 * [nvidia-driver-toolkit](./addons/nvidiadrivertoolkit)
 * [pcidevices-controller](./addons/pcidevices.md) 
 * [rancher-logging](../logging/harvester-logging.md)

diff --git a/versioned_docs/version-v1.6/advanced/addons/kubeovn-operator.md b/versioned_docs/version-v1.6/advanced/addons/kubeovn-operator.md
@@ -1,7 +1,7 @@
 ---
 sidebar_position: 9
 sidebar_label: Kube-OVN Operator
-title: "Kube-OVN Operator"
+title: "Kube-OVN Operator (Experimental)"
 ---
 
 <head>
@@ -10,6 +10,12 @@ title: "Kube-OVN Operator"
 
 _Available as of v1.6.0_
 
+:::note
+
+**kubeovn-operator** is an *experimental* add-on. For more information about experimental features, see [Feature Labels](../../getting-started/document-conventions.md#feature-labels).
+
+:::
+
 [`kubeovn-operator`](https://github.com/harvester/kubeovn-operator) is used to manage the lifecycle of [Kube-OVN](https://github.com/kubeovn/kube-ovn) as a secondary CNI on underlying Harvester clusters.
 
 ## Enabling `kubeovn-operator`

diff --git a/versioned_docs/version-v1.6/networking/kubeovn-vm-isolation.md b/versioned_docs/version-v1.6/networking/kubeovn-vm-isolation.md
@@ -15,6 +15,12 @@ keywords:
   <link rel="canonical" href="https://docs.harvesterhci.io/v1.6/networking/kubeovn-vm-isolation"/>
 </head>
 
+:::note
+
+All features that use Kube-OVN are considered experimental. For more information about experimental features, see [Feature Labels](../getting-started/document-conventions.md#feature-labels).
+
+:::
+
 Isolation between virtual machines is typically achieved using either VLANs (in traditional networks) or virtual switches (in Kube-OVN). If you want to isolate virtual machines within the same virtual switch network, you can use either of the following to achieve the required micro-segmentation:
 
 - Subnet access control lists (ACLs): Apply rules to a subnet used by virtual machines.

diff --git a/versioned_docs/version-v1.6/networking/kubeovn-vpc.md b/versioned_docs/version-v1.6/networking/kubeovn-vpc.md
@@ -16,6 +16,12 @@ keywords:
   <link rel="canonical" href="https://docs.harvesterhci.io/v1.6/networking/kubeovn-vpc"/>
 </head> 
 
+:::note
+
+All features that use Kube-OVN are considered experimental. For more information about experimental features, see [Feature Labels](../getting-started/document-conventions.md#feature-labels).
+
+:::
+
 A virtual private cloud (VPC) is a logically isolated network that provides full control over IP addresses, subnets, route tables, firewalls, and gateways within a cloud infrastructure. VPCs allow the secure and scalable deployment of virtualized resources such as compute, storage, and container services.
 
 The following table outlines the key components of a VPC: