tigergraph · wenbings · Jun 16, 2026 · Jun 16, 2026 · Jun 16, 2026
diff --git a/k8s/docs/01-introduction/README.md b/k8s/docs/01-introduction/README.md
@@ -15,6 +15,7 @@ Understanding the intricate synergy between TigerGraph, TigerGraph Operator, and
 
 | TigerGraph Operator version | TigerGraph version  | Kubernetes Validated version |
 |----------|----------|----------|
+| 1.7.2 | TigerGraph >= 3.6.0 && TigerGraph <= 4.3.0|1.30, 1.31, 1.32, 1.33, 1.34|
 | 1.7.1 | TigerGraph >= 3.6.0 && TigerGraph <= 4.3.0|1.30, 1.31, 1.32, 1.33, 1.34|
 | 1.7.0 | TigerGraph >= 3.6.0 && TigerGraph <= 4.3.0|1.27, 1.28, 1.29, 1.30, 1.31|
 | 1.6.0 | TigerGraph >= 3.6.0 && TigerGraph <= 4.2.2|1.27, 1.28, 1.29, 1.30, 1.31|

diff --git a/k8s/docs/04-manage/operator-upgrade.md b/k8s/docs/04-manage/operator-upgrade.md
@@ -6,7 +6,7 @@ This document provides step-by-step instructions for upgrading the TigerGraph Ku
   - [Before You begin](#before-you-begin)
     - [Release Number Definition](#release-number-definition)
     - [Check whether high availability is enabled on the TigerGraph Operator](#check-whether-high-availability-is-enabled-on-the-tigergraph-operator)
-  - [Upgrading from TigerGraph Operator 1.0.0 and later versions to version 1.7.1](#upgrading-from-tigergraph-operator-100-and-later-versions-to-version-171)
+  - [Upgrading from TigerGraph Operator 1.0.0 and later versions to version 1.7.2](#upgrading-from-tigergraph-operator-100-and-later-versions-to-version-172)
     - [Upgrading kubectl-tg plugin](#upgrading-kubectl-tg-plugin)
       - [Upgrading TigerGraph Operator](#upgrading-tigergraph-operator)
   - [Upgrading from TigerGraph Operator versions prior to 1.0.0 to version 1.0.0 and above](#upgrading-from-tigergraph-operator-versions-prior-to-100-to-version-100-and-above)
@@ -71,11 +71,11 @@ If the output above is 1, scale out the Operator with the following command:
 kubectl tg upgrade --namespace ${YOUR_NAMESPACE_OF_OPERATOR} --operator-size 3
 ```
 
-## Upgrading from TigerGraph Operator 1.0.0 and later versions to version 1.7.1
+## Upgrading from TigerGraph Operator 1.0.0 and later versions to version 1.7.2
 
 ### Upgrading kubectl-tg plugin
 
-To upgrade the kubectl-tg plugin for TigerGraph Operator 1.7.1, execute the following command:
+To upgrade the kubectl-tg plugin for TigerGraph Operator 1.7.2, execute the following command:
 
 ```bash
 curl https://dl.tigergraph.com/k8s/latest/kubectl-tg  -o kubectl-tg
@@ -87,7 +87,7 @@ Ensure you have installed the correct version of kubectl-tg:
 ```bash
 kubectl tg version
 
-Version: 1.7.1
+Version: 1.7.2
 Default version of TigerGraph cluster: 4.3.0
 ```
 
@@ -96,7 +96,7 @@ Default version of TigerGraph cluster: 4.3.0
 
 #### Upgrading TigerGraph Operator
 
-There are no breaking changes in the TigerGraph CRDs for version 1.7.1 compared to versions 1.0.0 and above. You can upgrade the TigerGraph Operator by following these steps if you have an older version (1.0.0 or above) installed.
+There are no breaking changes in the TigerGraph CRDs for version 1.7.2 compared to versions 1.0.0 and above. You can upgrade the TigerGraph Operator by following these steps if you have an older version (1.0.0 or above) installed.
 
 > [!IMPORTANT]
 > There is currently no support for upgrading or deleting CRDs when upgrading or uninstalling the TigerGraph Operator due to the risk of unintentional data loss. It is necessary to upgrade TigerGraph CRDs manually for the operator version prior to 1.3.0. However, starting from operator version 1.3.0, we use [Helm chart’s pre-upgrade hook](https://helm.sh/docs/topics/charts_hooks/) to upgrade the CRDs automatically. You can ignore the first step if you upgrade the operator to version 1.3.0 or above.
@@ -119,7 +119,7 @@ There are no breaking changes in the TigerGraph CRDs for version 1.7.1 compared
   helm list -n ${YOUR_NAMESPACE_OF_OPERATOR}
 
   NAME            NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                           APP VERSION      
-  tg-operator     tigergraph      2               2025-09-28 10:34:23.185036124 +0000 UTC deployed        tg-operator-1.7.1                1.7.1
+  tg-operator     tigergraph      2               2025-09-28 10:34:23.185036124 +0000 UTC deployed        tg-operator-1.7.2                1.7.2
   ```
 
 ## Upgrading from TigerGraph Operator versions prior to 1.0.0 to version 1.0.0 and above
@@ -195,7 +195,7 @@ Ensure you have installed the correct version of kubectl-tg:
 ```bash
 kubectl tg version
 
-Version: 1.7.1
+Version: 1.7.2
 Default version of TigerGraph cluster: 4.3.0
 ```
 
@@ -237,7 +237,7 @@ Ensure TigerGraph Operator has been installed successfully:
 helm list -n tigergraph
 
 NAME            NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                           APP VERSION      
-tg-operator     tigergraph      1               2025-09-10 10:34:23.185036124 +0000 UTC deployed        tg-operator-1.7.1                1.7.1
+tg-operator     tigergraph      1               2025-09-10 10:34:23.185036124 +0000 UTC deployed        tg-operator-1.7.2                1.7.2
 ```
 
 ```bash

diff --git a/k8s/docs/04-manage/tigergraph-upgrade.md b/k8s/docs/04-manage/tigergraph-upgrade.md
@@ -26,6 +26,7 @@ The synergy and compatibility between TigerGraph and TigerGraph Operator:
 
 | TigerGraph Operator version | TigerGraph version  |
 |----------|----------|
+| 1.7.2 | TigerGraph >= 3.6.0 && TigerGraph <= 4.3.0|
 | 1.7.1 | TigerGraph >= 3.6.0 && TigerGraph <= 4.3.0|
 | 1.6.0 | TigerGraph >= 3.6.0 && TigerGraph <= 4.2.1|
 | 1.5.0 | TigerGraph >= 3.6.0 && TigerGraph <= 4.2.0|
@@ -50,7 +51,7 @@ Example output:
 
 ```bash
 $ helm ls -A|grep tg-operator
-tg-operator             tigergraph      1               2026-05-05 04:53:01.952172143 +0000 UTC deployed      tg-operator-1.7.1               1.7.1      
+tg-operator             tigergraph      1               2026-05-05 04:53:01.952172143 +0000 UTC deployed      tg-operator-1.7.2               1.7.2      
 ```
 
 ## Upgrade the TigerGraph Cluster

diff --git a/k8s/docs/06-troubleshoot/cluster-management.md b/k8s/docs/06-troubleshoot/cluster-management.md
@@ -67,7 +67,7 @@ This document provides solutions for common issues that may arise during the man
     Image Pull Secrets:
       Name:  tigergraph-image-pull-secret
     Init Job:
-      Image:              docker.io/tigergraph/tigergraph-k8s-init:1.7.0
+      Image:              docker.io/tigergraph/tigergraph-k8s-init:1.7.2
       Image Pull Policy:  IfNotPresent
       Image Pull Secrets:
         Name:  tigergraph-image-pull-secret

diff --git a/k8s/docs/06-troubleshoot/operator-installation.md b/k8s/docs/06-troubleshoot/operator-installation.md
@@ -18,16 +18,16 @@ In the following steps, we assume that the TigerGraph Operator has been installe
   kubectl get deployment tigergraph-operator-controller-manager -o wide -n tigergraph
 
   NAME                                     READY   UP-TO-DATE   AVAILABLE   AGE   CONTAINERS   IMAGES                                               SELECTOR
-  tigergraph-operator-controller-manager   1/1     1            1           19d   manager      docker.io/tginternal/tigergraph-k8s-operator:1.7.1   control-plane=controller-manager
+  tigergraph-operator-controller-manager   1/1     1            1           19d   manager      docker.io/tginternal/tigergraph-k8s-operator:1.7.2   control-plane=controller-manager
   ```
 
-  From the output of the above command, you can figure out that the operator version is 1.7.1, docker.io/tigergraph/tigergraph-k8s-operator:1.7.1, you can also use the following helm command to get the current version of Operator:
+  From the output of the above command, you can figure out that the operator version is 1.7.2, docker.io/tigergraph/tigergraph-k8s-operator:1.7.2, you can also use the following helm command to get the current version of Operator:
 
   ```bash
   helm list -n tigergraph
 
   NAME            NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                   APP VERSION
-  tg-operator     tigergraph      1               2026-05-05 11:22:33.701059001 +0000 UTC deployed        tg-operator-1.7.1         1.7.1
+  tg-operator     tigergraph      1               2026-05-05 11:22:33.701059001 +0000 UTC deployed        tg-operator-1.7.2         1.7.2
 
   ```
 

diff --git a/k8s/docs/09-release-notes/README.md b/k8s/docs/09-release-notes/README.md
@@ -7,6 +7,7 @@ Those document describes the new features, improvements, bugfixes for all of Tig
 
 Please see the detailed documentation of each TigerGraph Operator version release notes as follows:
 
+- [TigerGraph Operator 1.7.2](./operator-1.7.2.md)
 - [TigerGraph Operator 1.7.1](./operator-1.7.1.md)
 - [TigerGraph Operator 1.7.0](./operator-1.7.0.md)
 - [TigerGraph Operator 1.6.0](./operator-1.6.0.md)

diff --git a/k8s/docs/09-release-notes/operator-1.7.2.md b/k8s/docs/09-release-notes/operator-1.7.2.md
@@ -0,0 +1,65 @@
+# TigerGraph Operator 1.7.2 Release notes
+
+## Overview
+
+**TigerGraph Operator 1.7.2** is now available, designed to work seamlessly with **TigerGraph version 4.3.0**.
+
+This release is a patch version of 1.7.1. There are no new features, just some improvements and bug fixes.
+
+For further details, see the sections below.
+
+> [!IMPORTANT]
+> TigerGraph Operator has had a breaking change since version 1.0.0. If you are still using a version older than 1.0.0, it is strongly recommended that you upgrade to version 1.7.2. Versions older than 1.0.0 have been deprecated.
+
+### kubectl plugin installation
+
+To install the kubectl plugin for TigerGraph Operator 1.7.2, execute the following command:
+
+```bash
+curl https://dl.tigergraph.com/k8s/1.7.2/kubectl-tg  -o kubectl-tg
+sudo install kubectl-tg /usr/local/bin/
+```
+
+### TigerGraph Operator upgrading
+
+#### Upgrading from TigerGraph Operator 1.0.0+ to 1.7.2
+
+There are no breaking changes in the Custom Resource Definitions (CRDs) for version 1.7.2 compared to versions 1.0.0 and above. If you are running Operator 1.0.0 or later, upgrade using the following command:
+
+> [!NOTE]
+> There is currently no support for upgrading or deleting CRDs when upgrading or uninstalling the TigerGraph Operator due to the risk of unintentional data loss. It is necessary to upgrade TigerGraph CRDs manually for the operator version prior to 1.3.0. However, starting from Operator version 1.3.0, we use [Helm chart's pre-upgrade hook](https://helm.sh/docs/topics/charts_hooks/) to upgrade the CRDs automatically. You can ignore the first step if you upgrade the operator to version 1.3.0 or above.
+
+> [!IMPORTANT]
+> Please ensure that you have installed the `kubectl-tg` version 1.7.2 before upgrading TigerGraph Operator to version 1.7.2.
+
+Ensure you have installed the correct version of kubectl-tg:
+
+```bash
+kubectl tg version
+
+Version: 1.7.2
+Default version of TigerGraph cluster: 4.3.0
+```
+
+Upgrade TigerGraph Operator using kubectl-tg plugin:
+
+```bash
+kubectl tg upgrade --namespace ${YOUR_NAMESPACE_OF_OPERATOR} --operator-version 1.7.2
+```
+
+#### Upgrading from TigerGraph Operator Versions Prior to 1.0.0
+
+This TigerGraph Operator version upgrade introduces breaking changes if you are upgrading from TigerGraph Operator versions prior to 1.0.0. You need to upgrade the TigerGraph Operator, CRD, and the TigerGraph cluster following specific steps.
+
+Refer to the documentation [How to upgrade TigerGraph Kubernetes Operator](../04-manage/operator-upgrade.md) for details.
+
+
+## Improvements
+
+- Made the operator upgrade job's CPU and memory resources configurable, giving you more control over resource usage during upgrades;
+
+## Bug Fixes
+
+- Fixed a LoadBalancer provisioning race condition by serializing external LB teardown — the operator now waits for the service to be fully removed before recreating it, preventing conflicts during pause, listener removal, and service type changes;
+- Improved pod startup reliability during cluster operations such as restarts and recreations;
+- Improved cluster startup stability;