From 66fd617cd823834db919c781d589108c6f931b7b Mon Sep 17 00:00:00 2001
From: Wenbing Sun <wenbing.sun@tigergraph.com>
Date: Mon, 31 Aug 2026 13:12:30 -0700
Subject: [PATCH] add release note for operator 1.7.4

---
 k8s/docs/09-release-notes/operator-1.7.4.md | 64 +++++++++++++++++++++
 1 file changed, 64 insertions(+)
 create mode 100644 k8s/docs/09-release-notes/operator-1.7.4.md

diff --git a/k8s/docs/09-release-notes/operator-1.7.4.md b/k8s/docs/09-release-notes/operator-1.7.4.md
new file mode 100644
index 00000000..2e1a693d
--- /dev/null
+++ b/k8s/docs/09-release-notes/operator-1.7.4.md
@@ -0,0 +1,64 @@
+# TigerGraph Operator 1.7.4 Release notes
+
+## Overview
+
+**TigerGraph Operator 1.7.4** is now available, designed to work seamlessly with **TigerGraph version 4.3.0**.
+
+This release is a patch version of 1.7.3. There are no new features, only 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.4. Versions older than 1.0.0 have been deprecated.
+
+### kubectl plugin installation
+
+To install the kubectl plugin for TigerGraph Operator 1.7.4, execute the following command:
+
+```bash
+curl https://dl.tigergraph.com/k8s/1.7.4/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.4
+
+There are no breaking changes in the Custom Resource Definitions (CRDs) for version 1.7.4 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.4 before upgrading TigerGraph Operator to version 1.7.4.
+
+Ensure you have installed the correct version of kubectl-tg:
+
+```bash
+kubectl tg version
+
+Version: 1.7.4
+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.4
+```
+
+#### 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.
+
+
+## Bug Fixes
+
+- Fixed an issue for TG maintenance release upgrade with nginx config template change;
+- Set fsGroupChangePolicy OnRootMismatch to reduce pod startup time;
+- CVE fix: upgrade openssh in init container;
+- CVE fix: bump golang.org/x/crypto in k8s-operator;
+- CVE fix: bump golang.org/x/net and golang.org/x/text in k8s-operator;
+- CVE fix: bump grpc and cel-go for GHSA-hrxh-6v49-42gf, GHSA-gcjh-h69q-9w9g;
\ No newline at end of file