Merge branch 'internal/nginxaas-next' into internal/nginxaas-billing

Author: JTorreG

content/includes/nginxaas-google/update-nginx-config.md

@@ -5,7 +5,7 @@ nd-docs: DOCS-000
 1. On the left menu, select **Configurations**.
 1. On the list of configurations, select the ellipses (three dots) icon next to the configuration you want to update.
 1. Select **Edit**.
-1. Update the "Name" and "Description" fields as needed and select **Next**.
+1. Update the "Description" field as needed and select **Next**.
 1. Select the file you want to update in the file tree.
    - Certificates can only be copied, moved, or renamed.
 1. Modify the configuration file(s) as needed and select **Next**.

content/nginxaas-azure/get-help/support.md

@@ -14,25 +14,23 @@ To contact support about F5 NGINXaaS for Azure (NGINXaaS):
 
 1. Go to your NGINXaaS deployment.
 
-2. Select **New Support request** in the left menu.
+1. Select **New Support request** in the left menu.
 
-3. Select **Raise a Support ticket**.
+1. Select **Raise a Support ticket**.
 
    {{< img src="nginxaas-azure/raise-ticket.png" alt="Screenshot of the Azure portal showing the Raise support ticket button" >}}
 
-4. You will be redirected to **MyF5** to create a new case. Log in to MyF5 with your F5 account.
+1. You will be redirected to **MyF5** to create a new case. Log in to MyF5 with your F5 account.
 
 {{< call-out "note" >}}If you can't complete a deployment successfully, the "New support request" option won't be available on the left-hand navigation menu. To raise a support ticket, go to the [MyF5 portal](https://my.f5.com). {{< /call-out >}}
 
-5. Go to the **Case Management** section and select **Create new case**.
-
-   {{< img src="nginxaas-azure/new-case.png" alt="Screenshot of the MyF5 portal showing the Create new case button" >}}
+1. Go to the **Support** section and select **Create a Case**.
 
-6. Select **NGINXaaS** in the Product dropdown.
+1. Select **NGINX Products** as the product family.
 
-   {{< img src="nginxaas-azure/create-case.png" alt="MyF5 Case form" >}}
+1. Select **NGINXaaS for Azure** in the Product dropdown.
 
-7. Complete the request with the relevant information about your issue, bug report, or feedback. If you are contacting us to report an issue, please include the following information, available in the **Properties** section of your deployment, for the support team to begin their investigation:
+1. Complete the request with the relevant information about your issue, bug report, or feedback. If you are contacting us to report an issue, please include the following information, available in the **Properties** section of your deployment, for the support team to begin their investigation:
 
 - Location
 - Date and time of the issue
@@ -45,7 +43,7 @@ If your deployment is configured to use F5 WAF for NGINX, please collect the fol
 
 {{< img src="nginxaas-azure/properties.png" alt="Screenshot of the Azure portal showing the Properties section" >}}
 
-8. Complete the **Additional information** and **Contact details** sections of your case and select **Submit**.
+1. Complete the **Additional information** and **Contact details** sections of your case and select **Submit**.
 
 ## Update support contact information
 

content/nginxaas-google/changelog.md

@@ -11,6 +11,32 @@ Learn about the latest updates, new features, and resolved bugs in F5 NGINXaaS f
 
 To see a list of currently active issues, visit the [Known issues]({{< ref "/nginxaas-google/known-issues.md" >}}) page.
 
+## October 13, 2025
+
+- {{% icon-feature %}} **NGINXaaS for Google Cloud is generally available**
+
+We are pleased to announce the general availability of F5 NGINXaaS for Google Cloud.
+
+F5 NGINXaaS for Google Cloud is a fully managed load balancer and application delivery service that streamlines cloud-native application delivery without the operational complexity of managing infrastructure. This service simplifies the deployment of APIs, microservices, and web applications while enhancing performance, visibility, security, and scalability in Google Cloud.
+
+Key features include adaptive load balancing, advanced connectivity patterns for deployment strategies like blue-green and canary, detailed visibility with over 200 real-time metrics, and strong security controls such as role-based access control and end-to-end encryption. The service also consolidates technology with unified L4/L7 load balancing combined with advanced security and programmability into a single platform for enhanced operational efficiency.
+
+This announcement marks a significant step in application delivery modernization, empowering organizations to improve user experiences and achieve seamless integration with Google Cloud Monitoring.
+
+To learn more, refer to the following resources:
+
+- **Product Information:**
+	
+    - [F5 NGINXaaS for Google Cloud](https://www.f5.com/products/nginx/f5-nginxaas-for-google-cloud)
+    - [Overview and architecture]({{< ref "/nginxaas-google/overview/overview.md" >}})
+    - [Getting Started]({{< ref "/nginxaas-google/getting-started/prerequisites/" >}})
+	
+- **Blogs:** [F5 NGINXaaS for Google Cloud: Delivering resilient, scalable applications ](https://f5.com/company/blog/delivering-resilient-scalable-applications.html)
+- **Webinars:** [Why F5 NGINXaaS for Google Cloud is a game changer](https://events.actualtechmedia.com/on-demand/1603/why-f5-nginxaas-for-google-cloud-is-a-game-changer/)
+
+Visit the Google Cloud Marketplace and start leveraging NGINXaaS for Google Cloud today!
+
+
 ## September 18, 2025
 
 - {{% icon-feature %}} **NGINXaaS for Google Cloud Early Access**

content/nginxaas-google/get-help.md

@@ -0,0 +1,5 @@
+---
+title: Get help
+weight: 700
+url: /nginxaas/google/get-help/
+---

content/nginxaas-google/get-help/_index.md

@@ -0,0 +1,41 @@
+---
+title: Support
+weight: 100
+toc: true
+nd-docs: DOCS-000
+url: /nginxaas/googoe/get-help/support
+type:
+- how-to
+---
+
+## Contact F5 support
+
+To contact support about F5 NGINXaaS for Google Cloud (NGINXaaS):
+
+1. Go to the [MyF5 portal](https://my.f5.com) and log in with your F5 account.
+
+1. Go to the **Support** section and select **Create a Case**.
+
+1. Select **NGINX Products** as the product family.
+
+1. Select **NGINXaaS for Google Cloud** in the Product dropdown.
+
+1. Fill out the**Subject** and **Description** sections, and include the following details about the specific issue:
+
+    1. Identifying Information:
+       - Deployment identifier (Object ID and name)
+       - Account identifier/name
+    1. Issue Details:
+       - A detailed description of the issue
+       - The specific resources involved (for example: deployment, configuration, certificate, and so on)
+       - The operation you were performing when the issue occurred (for example: creating a deployment, uploading a configuration, adding a certificate, and so on)
+       - Any error messages displayed
+       - The time when the issue occurred
+
+1. Fill out the fields in the **Additional information** section including: 
+
+    - **Subscription ID**: select your F5 or NGINX subscription ID (use `No subscription available` if you don't have one)
+    - **Assign a priority**
+    - **Reason for contact**
+
+1. Complete the **Contact details** section of your case and select **Submit**.

content/nginxaas-google/get-help/support.md

@@ -0,0 +1,9 @@
+---
+title: Troubleshooting guide
+toc: false
+url: /nginxaas/google/get-help/troubleshooting
+weight: 300
+draft: true
+---
+
+<!-- this dummy doc is used to create a list page entry that redirects users to the troubleshooting guide in the F5 knowledge base. The redirect is configured in google-redirects-base -->

content/nginxaas-google/get-help/troubleshooting.md

@@ -75,7 +75,7 @@ In the NGINXaaS Console,
 
 1. To open the details of your deployment, select its name from the list of deployments.
    - You can view the details of your deployment, including the status, region, network attachment, NGINX configuration, and more.
-1. Select **Edit** to modify the deployment name, description, and NCU Capacity.
+1. Select **Edit** to modify the deployment description, and NCU Capacity.
    - You can also configure monitoring from here. Detailed instructions can be found in [Enable Monitoring]({{< ref "/nginxaas-google/monitoring/enable-monitoring.md" >}})
 1. Select **Update** to save your changes.
 1. Select the Configuration tab to view the current NGINX configuration associated with the deployment.

content/nginxaas-google/getting-started/create-deployment/deploy-console.md

@@ -27,18 +27,11 @@ An existing NGINXaaS Account user can add additional users following these steps
 1. Access the [NGINXaaS Console](https://console.nginxaas.net/).
 1. Log in to the console with your Google credentials.
 1. Navigate to **Users** page on the left menu, then select **Add User**.
-1. Enter the **Name** and **Email** for the user to be added. The email must match the individual's Google User to be able to authenticate successfully.
+1. Enter the **Email** address for the user to be added. The email must match the individual's Google User to be able to authenticate successfully.
 1. Select **Create User** to save the changes.
 
 The new user will appear in the list of users on the **Users** page. Their **Google Identity Domain** will remain empty until they log in for the first time.
 
-### Edit a user
-
-1. Select **Users** under the **Settings** section on the left menu.
-1. Select the ellipsis (three dots) menu for the user you want to update.
-1. Select **Edit** and update the user details.
-1. Select **Update** to confirm the changes.
-
 ## Modify account settings
 
 As an authenticated user, you may modify the authorized domains and name of an NGINXaaS Account.

content/nginxaas-google/getting-started/manage-users-accounts.md

@@ -43,11 +43,11 @@ Refer to the [Google's Metrics Explorer](https://cloud.google.com/monitoring/cha
 
 You can retrieve raw time series metrics from the [Cloud Monitoring API](https://cloud.google.com/monitoring/api/v3).
 
-For example, you can use [`projects.timeSeries.list`](https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.timeSeries/list) to list metrics matching filters from a specified time interval. The following `curl` command lists `nginxaas.ncus.provisioned` metrics from the time interval `start_time` to `end_time` in the given `project_id`.
+For example, you can use [`projects.timeSeries.list`](https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.timeSeries/list) to list metrics matching filters from a specified time interval. The following `curl` command lists `nginx.http.requests` metrics from the time interval `start_time` to `end_time` in the given `project_id`.
 
 ```bash
 curl \
-  "https://monitoring.googleapis.com/v3/projects/{project_id}/timeSeries?filter=metric.type%3D%22workload.googleapis.com%2Fnginxaas.ncus.provisioned%22&interval.endTime={end_time}&interval.startTime={start_time}" \
+  "https://monitoring.googleapis.com/v3/projects/{project_id}/timeSeries?filter=metric.type%3D%22workload.googleapis.com%2Fnginx.http.requests%22&interval.endTime={end_time}&interval.startTime={start_time}" \
   --header "Authorization: Bearer $(gcloud auth print-access-token)" \
   --header "Accept: application/json" \
   --compressed
@@ -71,7 +71,7 @@ The following JSON shows an example response body:
           "nginxaas_deployment_name": "test-deployment",
           "nginxaas_namespace": "default"
         },
-        "type": "workload.googleapis.com/nginxaas.ncus.provisioned"
+        "type": "workload.googleapis.com/nginx.http.requests"
       },
       "resource": {
         "type": "generic_node",
@@ -82,7 +82,7 @@ The following JSON shows an example response body:
           "project_id": "{project_id}"
         }
       },
-      "metricKind": "GAUGE",
+      "metricKind": "CUMULATIVE",
       "valueType": "INT64",
       "points": [
         {
@@ -91,7 +91,7 @@ The following JSON shows an example response body:
             "endTime": "{end_time}"
           },
           "value": {
-            "int64Value": "10"
+            "int64Value": "1405"
           }
         }
       ]