From 36816522207ac52b62d5836b5d04a84440dadab8 Mon Sep 17 00:00:00 2001 From: Saylor Berman Date: Thu, 6 Mar 2025 08:25:46 -0700 Subject: [PATCH] docs: NGF - add more context to Secret duplication Mention that users can update the original Secrets to propagate changes to duplicate Secrets. --- content/ngf/installation/nginx-plus-jwt.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/ngf/installation/nginx-plus-jwt.md b/content/ngf/installation/nginx-plus-jwt.md index 7d7fcbdb5..7f22f9d9b 100644 --- a/content/ngf/installation/nginx-plus-jwt.md +++ b/content/ngf/installation/nginx-plus-jwt.md @@ -15,7 +15,7 @@ This requirement is part of F5’s broader licensing program and aligns with ind The JWT is required for validating your subscription and reporting telemetry data. For environments connected to the internet, telemetry is automatically sent to F5’s licensing endpoint. In offline environments, telemetry is routed through [NGINX Instance Manager](https://docs.nginx.com/nginx-instance-manager/). Usage is reported every hour and on startup whenever NGINX is reloaded. -{{< note >}} The following Secrets should be created in the same namespace as the NGINX Gateway Fabric control plane (default: nginx-gateway). The control plane will copy these Secrets into any namespaces where NGINX gets deployed. {{< /note >}} +{{< note >}} The following Secrets should be created in the same namespace as the NGINX Gateway Fabric control plane (default: nginx-gateway). The control plane will copy these Secrets into any namespaces where NGINX gets deployed. If you need to update the Secrets, update the originals that you created in the control plane namespace, and the control plane will propagate those updates to all duplicated Secrets. {{< /note >}} ---