diff --git a/content/rancher/v2.6/en/cluster-admin/editing-clusters/gke-config-reference/_index.md b/content/rancher/v2.6/en/cluster-admin/editing-clusters/gke-config-reference/_index.md
index 528d19659c0..b602172275e 100644
--- a/content/rancher/v2.6/en/cluster-admin/editing-clusters/gke-config-reference/_index.md
+++ b/content/rancher/v2.6/en/cluster-admin/editing-clusters/gke-config-reference/_index.md
@@ -57,6 +57,12 @@ _Mutable: yes_
 
 Enable network policy enforcement on the cluster. A network policy defines the level of communication that can occur between pods and services in the cluster. For more information, refer to [this page.](https://cloud.google.com/kubernetes-engine/docs/how-to/network-policy)
 
+### Project Network Isolation
+
+_Mutable: yes_
+
+choose whether to enable or disable inter-project communication. Note that enabling Project Network Isolation will automatically enable Network Policy and Network Policy Config, but not vice versa.
+
 ### Node Ipv4 CIDR Block
 
 _Mutable: no_
@@ -222,6 +228,14 @@ You can apply labels to the node pool, which applies the labels to all nodes in
 
 Invalid labels can prevent upgrades or can prevent Rancher from starting. For details on label syntax requirements, see the [Kubernetes documentation.](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set)
 
+### Network Tags
+
+_Mutable: no_
+
+You can add network tags to the node pool to make firewall rules and routes between subnets. Tags will apply to all nodes in the pool.
+
+For details on tag syntax and requirements, see the [Kubernetes documentation](https://cloud.google.com/vpc/docs/add-remove-network-tags).
+
 # Group Details
 
 In this section, enter details describing the node pool.