diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS index 392b2ecac..c21aa2244 100644 --- a/.github/CODEOWNERS +++ b/.github/CODEOWNERS @@ -53,5 +53,5 @@ content/nim/* @nginx/nim-docs-approvers content/nginx/* @nginx/plus-docs-approvers # NGINX One -content/nginx-one/* @nginx/one-docs-approvers +content/nginx-one-console/* @nginx/one-docs-approvers diff --git a/.github/labeler.yml b/.github/labeler.yml index d3684b539..f5092e5ca 100644 --- a/.github/labeler.yml +++ b/.github/labeler.yml @@ -55,11 +55,11 @@ product/nginx-plus: - 'content/nginx/**' - 'content/includes/nginx-plus/**' -product/nginx-one: +product/nginx-one-console: - changed-files: - any-glob-to-any-file: - - 'content/nginx-one/**' - - 'content/includes/nginx-one/**' + - 'content/nginx-one-console/**' + - 'content/includes/nginx-one-console/**' product/nginxaas-azure: - changed-files: diff --git a/_banners/agent-v3-release.md b/_banners/agent-v3-release.md index 87bd0021a..02b8c6ef6 100644 --- a/_banners/agent-v3-release.md +++ b/_banners/agent-v3-release.md @@ -1,6 +1,6 @@ {{< banner "notice" "NGINX Agent 3.0 is now available" >}} -The documentation in this section is for **NGINX Agent version 2.x**. For NGINX Agent 3.x content visit the [NGINX One Console documentation]({{< ref "/nginx-one/agent/" >}}) +The documentation in this section is for **NGINX Agent version 2.x**. For NGINX Agent 3.x content visit the [NGINX One Console documentation]({{< ref "/nginx-one-console/agent/" >}}) F5 NGINX Instance Manager (NIM) does not currently support NGINX Agent 3.x. NGINX Instance Manager customers can upgrade to the latest NGINX Agent 2.x version by following the [Upgrade NGINX Agent](/nginx-agent/installation-upgrade/upgrade/) guide. diff --git a/_banners/eol-amplify.md b/_banners/eol-amplify.md index 0f70571c4..9060ac97a 100644 --- a/_banners/eol-amplify.md +++ b/_banners/eol-amplify.md @@ -6,7 +6,7 @@ NGINX Amplify support ends on January 31, 2026. To continue monitoring your NGIN 1. [Contact the F5 NGINX Sales team](https://www.f5.com/products/get-f5/f5-nginx-products-and-packaging) to get an NGINX One subscription, if you don’t already have one. 2. [Uninstall the NGINX Amplify agent]({{< ref "/amplify/nginx-amplify-agent/install/uninstalling-amplify-agent.md" >}}). -3. [Follow the NGINX One Console getting started guide]({{< ref "/nginx-one/getting-started.md" >}}). +3. [Follow the NGINX One Console getting started guide]({{< ref "/nginx-one-console/getting-started.md" >}}). [Professional Services](https://www.f5.com/services) are available to support your transition. Additional fees may apply. {{}} \ No newline at end of file diff --git a/content/_index.md b/content/_index.md index ddabc2178..0fdb961ed 100644 --- a/content/_index.md +++ b/content/_index.md @@ -7,7 +7,7 @@ description: Learn how to deliver, manage, and protect your applications using F Learn how to deliver, manage, and protect your applications using F5 NGINX products. {{}} - {{}} + {{}} Monitor your infrastructure, address security vulnerabilities, and assess the health of your NGINX fleet, all from a single console. {{}} {{}} diff --git a/content/agent/contribute/dev-environment-setup.md b/content/agent/contribute/dev-environment-setup.md index 72827ceba..23ed71989 100644 --- a/content/agent/contribute/dev-environment-setup.md +++ b/content/agent/contribute/dev-environment-setup.md @@ -17,7 +17,7 @@ Ubuntu is the recommended operating system for development, as it comes with mos To begin this task, you will require the following: -- A [working NGINX Agent instance]({{< ref "/nginx-one/agent/install-upgrade/" >}}). +- A [working NGINX Agent instance]({{< ref "/nginx-one-console/agent/install-upgrade/" >}}). - A [Go installation](https://go.dev/dl/) of version 1.22.2 or newer. - A [Protocol Buffer Compiler](https://grpc.io/docs/protoc-installation/) installation. @@ -29,7 +29,7 @@ git clone git@github.com:nginx/agent.git Read [Cloning a repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository) for more information -Follow the steps in the [Installation]({{< ref "/nginx-one/agent/install-upgrade/" >}}) topic to install NGINX Agent. +Follow the steps in the [Installation]({{< ref "/nginx-one-console/agent/install-upgrade/" >}}) topic to install NGINX Agent. ## Install prerequisite packages Depending on the operating system distribution, it may be necessary to install the following packages in order to build NGINX Agent. diff --git a/content/agent/contribute/start-mock-interface.md b/content/agent/contribute/start-mock-interface.md index 9b338d09f..4fc9c2e7b 100644 --- a/content/agent/contribute/start-mock-interface.md +++ b/content/agent/contribute/start-mock-interface.md @@ -14,7 +14,7 @@ The mock interface is useful when developing NGINX Agent, as it allows you to vi To begin this task, you will require the following: -- A [working NGINX Agent instance]({{< ref "/nginx-one/agent/install-upgrade/" >}}). +- A [working NGINX Agent instance]({{< ref "/nginx-one-console/agent/install-upgrade/" >}}). - A [Go installation](https://go.dev/dl/) of version 1.22.2 or newer. - A [go-swagger](https://goswagger.io/go-swagger/install/) installation. diff --git a/content/glossary/glossary.md b/content/glossary/glossary.md index 4a306b0ff..91c033b59 100644 --- a/content/glossary/glossary.md +++ b/content/glossary/glossary.md @@ -15,13 +15,13 @@ This glossary defines terms used in F5 NGINX. | Term | Definition | | ---- | ---------- | -| **Config Sync Group** / **Instance Group** | A group of NGINX systems (or instances) with identical configurations. They may also share the same certificates. However, the instances in a Config Sync Group could belong to different systems and even different clusters. Also known as an Instance Group in NGINX Instance Manager. For more information, see this explanation of [Important considerations]({{< ref "/nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups.md#important-considerations" >}}) | +| **Config Sync Group** / **Instance Group** | A group of NGINX systems (or instances) with identical configurations. They may also share the same certificates. However, the instances in a Config Sync Group could belong to different systems and even different clusters. Also known as an Instance Group in NGINX Instance Manager. For more information, see this explanation of [Important considerations]({{< ref "/nginx-one-console/nginx-configs/config-sync-groups/manage-config-sync-groups.md#important-considerations" >}}) | | **Control Plane** | The control plane is the part of a network architecture that manages and controls the flow or data or traffic (the Data Plane). It is responsible for system-level tasks such as routing and traffic management. | | **Data Plane** | The data plane is the part of a network architecture that carries user traffic. It handles tasks like forwarding data packets between devices and managing network communication. In the context of NGINX, the data plane is responsible for tasks such as load balancing, caching, and serving web content. | | **Instance** | An instance is an individual system with NGINX installed. You can group the instances of your choice in a Config Sync Group. When you add an instance to NGINX One Console, you need to use a data plane key. | | **Namespace** | In F5 Distributed Cloud, a namespace groups a tenant's configuration objects, similar to administrative domains. Every object in a namespace must have a unique name, and each namespace must be unique to its tenant. This setup ensures isolation, preventing cross-referencing of objects between namespaces. You'll see the namespace in the NGINX One Console URL as `/namespaces//`. To switch an instance between namespaces, you have to deregister an instance from an old namespace, and register it on the new namespace. | | **NGINX Agent** | A lightweight software component installed on NGINX instances to enable communication with the NGINX One console. NGINX Agent also enables communication with NGINX Instance Manager. | -| **Staged Configurations** | Also known as **Staged Configs**. Allows you to save "work in progress." You can create it from scratch, an Instance, another Staged Config, or a Config Sync Group. It does _not_ have to be a working configuration until you publish it to an instance or a Config Sync Group. You can even manage your **Staged Configurations** through our [API]({{< ref "/nginx-one/api/api-reference-guide/#tag/StagedConfigs" >}}). | +| **Staged Configurations** | Also known as **Staged Configs**. Allows you to save "work in progress." You can create it from scratch, an Instance, another Staged Config, or a Config Sync Group. It does _not_ have to be a working configuration until you publish it to an instance or a Config Sync Group. You can even manage your **Staged Configurations** through our [API]({{< ref "/nginx-one-console/api/api-reference-guide/#tag/StagedConfigs" >}}). | | **Tenant** | A tenant in F5 Distributed Cloud is an entity that owns a specific set of configuration and infrastructure. It is fundamental for isolation, meaning a tenant cannot access objects or infrastructure of other tenants. Tenants can be either individual or enterprise, with the latter allowing multiple users with role-based access control (RBAC). | {{< /table >}} @@ -62,9 +62,9 @@ It assumes you are familiar with various layer 7 (L7) hypertext transfer protoco ## NGINX Alerts -To set up NGINX Alerts through the F5 Distributed Cloud, follow the procedure in [Set up security alerts]({{< ref "/nginx-one/secure-your-fleet/set-up-security-alerts/" >}}). +To set up NGINX Alerts through the F5 Distributed Cloud, follow the procedure in [Set up security alerts]({{< ref "/nginx-one-console/secure-your-fleet/set-up-security-alerts/" >}}). -{{< include "/nginx-one/alert-labels.md" >}} +{{< include "/nginx-one-console/alert-labels.md" >}} ## References diff --git a/content/includes/agent/about.md b/content/includes/agent/about.md index fccce5514..2c66ed327 100644 --- a/content/includes/agent/about.md +++ b/content/includes/agent/about.md @@ -1,7 +1,7 @@ --- files: - content/agent/about.md - - content/nginx-one/agent/overview/about.md + - content/nginx-one-console/agent/overview/about.md --- F5 NGINX Agent is a lightweight companion daemon designed to work with NGINX One and enable remote management of NGINX instances. It also gathers performance metrics from NGINX and transmits them to the NGINX One Console for enhanced monitoring and control. @@ -12,14 +12,14 @@ Enable Access to key NGINX One use cases: - Seamlessly integrates with essential NGINX One functionality, simplifying access to its core use cases and enhancing operational workflows. - - [Connects NGINX instances to NGINX One Console]({{< ref "/nginx-one/agent/install-upgrade/install-from-oss-repo.md#connect-an-instance-to-nginx-one-console" >}}) + - [Connects NGINX instances to NGINX One Console]({{< ref "/nginx-one-console/agent/install-upgrade/install-from-oss-repo.md#connect-an-instance-to-nginx-one-console" >}}) Real-time observability into NGINX One data plane instances: - Provides live monitoring and actionable insights into the performance, status, and health of NGINX One data plane instances, improving decision-making and operational efficiency. - NGINX Agent supports [OpenTelemetry](https://opentelemetry.io/) and the ability to - [export the metrics data]({{< ref "/nginx-one/agent/configure-otel-metrics.md" >}}) for use in other applications. + [export the metrics data]({{< ref "/nginx-one-console/agent/configure-otel-metrics.md" >}}) for use in other applications. diff --git a/content/includes/agent/architecture.md b/content/includes/agent/architecture.md index f0b7c80cf..288578976 100644 --- a/content/includes/agent/architecture.md +++ b/content/includes/agent/architecture.md @@ -1,7 +1,7 @@ --- files: - content/agent/about.md - - content/nginx-one/agent/overview/about.md + - content/nginx-one-console/agent/overview/about.md --- The figure shows: diff --git a/content/includes/agent/installation/manually-connect-to-console.md b/content/includes/agent/installation/manually-connect-to-console.md index 365c514e4..fc62d529c 100644 --- a/content/includes/agent/installation/manually-connect-to-console.md +++ b/content/includes/agent/installation/manually-connect-to-console.md @@ -1,8 +1,8 @@ --- files: - - content/nginx-one/agent/install-upgrade/install-from-github.md - - content/nginx-one/agent/install-upgrade/install-from-oss-repo.md - - content/nginx-one/agent/install-upgrade/install-from-plus-repo.md + - content/nginx-one-console/agent/install-upgrade/install-from-github.md + - content/nginx-one-console/agent/install-upgrade/install-from-oss-repo.md + - content/nginx-one-console/agent/install-upgrade/install-from-plus-repo.md --- If you have installed NGINX Agent manually, you will need to connect it to the diff --git a/content/includes/agent/installation/oss/oss-alpine.md b/content/includes/agent/installation/oss/oss-alpine.md index 0c9289b67..efb7709bb 100644 --- a/content/includes/agent/installation/oss/oss-alpine.md +++ b/content/includes/agent/installation/oss/oss-alpine.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/install-from-oss-repo.md - - content/nginx-one/agent/install-upgrade/install-from-oss-repo.md + - content/nginx-one-console/agent/install-upgrade/install-from-oss-repo.md --- 1. Install the prerequisites: diff --git a/content/includes/agent/installation/oss/oss-amazon-linux.md b/content/includes/agent/installation/oss/oss-amazon-linux.md index d13a1a6e9..1cd44c58d 100644 --- a/content/includes/agent/installation/oss/oss-amazon-linux.md +++ b/content/includes/agent/installation/oss/oss-amazon-linux.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/install-from-oss-repo.md - - content/nginx-one/agent/install-upgrade/install-from-oss-repo.md + - content/nginx-one-console/agent/install-upgrade/install-from-oss-repo.md --- 1. Install the prerequisites: diff --git a/content/includes/agent/installation/oss/oss-debian.md b/content/includes/agent/installation/oss/oss-debian.md index de5113058..e405b52da 100644 --- a/content/includes/agent/installation/oss/oss-debian.md +++ b/content/includes/agent/installation/oss/oss-debian.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/install-from-oss-repo.md - - content/nginx-one/agent/install-upgrade/install-from-oss-repo.md + - content/nginx-one-console/agent/install-upgrade/install-from-oss-repo.md --- 1. Install the prerequisites: diff --git a/content/includes/agent/installation/oss/oss-freebsd.md b/content/includes/agent/installation/oss/oss-freebsd.md index 78496f76c..f051fe620 100644 --- a/content/includes/agent/installation/oss/oss-freebsd.md +++ b/content/includes/agent/installation/oss/oss-freebsd.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/install-from-oss-repo.md - - content/nginx-one/agent/install-upgrade/install-from-oss-repo.md + - content/nginx-one-console/agent/install-upgrade/install-from-oss-repo.md --- 1. To setup the pkg repository create a file with name `/etc/pkg/nginx-agent.conf` diff --git a/content/includes/agent/installation/oss/oss-rhel.md b/content/includes/agent/installation/oss/oss-rhel.md index 45c83c7ad..61650799d 100644 --- a/content/includes/agent/installation/oss/oss-rhel.md +++ b/content/includes/agent/installation/oss/oss-rhel.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/install-from-oss-repo.md - - content/nginx-one/agent/install-upgrade/install-from-oss-repo.md + - content/nginx-one-console/agent/install-upgrade/install-from-oss-repo.md --- 1. Install the prerequisites: diff --git a/content/includes/agent/installation/oss/oss-sles.md b/content/includes/agent/installation/oss/oss-sles.md index d082e522a..f859dc062 100644 --- a/content/includes/agent/installation/oss/oss-sles.md +++ b/content/includes/agent/installation/oss/oss-sles.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/install-from-oss-repo.md - - content/nginx-one/agent/install-upgrade/install-from-oss-repo.md + - content/nginx-one-console/agent/install-upgrade/install-from-oss-repo.md --- 1. Install the prerequisites: diff --git a/content/includes/agent/installation/oss/oss-ubuntu.md b/content/includes/agent/installation/oss/oss-ubuntu.md index f493e71a2..f7f310942 100644 --- a/content/includes/agent/installation/oss/oss-ubuntu.md +++ b/content/includes/agent/installation/oss/oss-ubuntu.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/install-from-oss-repo.md - - content/nginx-one/agent/install-upgrade/install-from-oss-repo.md + - content/nginx-one-console/agent/install-upgrade/install-from-oss-repo.md --- 1. Install the prerequisites: diff --git a/content/includes/agent/installation/plus/plus-alpine.md b/content/includes/agent/installation/plus/plus-alpine.md index 4c0570314..86666bbd8 100644 --- a/content/includes/agent/installation/plus/plus-alpine.md +++ b/content/includes/agent/installation/plus/plus-alpine.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/install-from-plus-repo.md - - content/nginx-one/agent/install-upgrade/install-from-plus-repo.md + - content/nginx-one-console/agent/install-upgrade/install-from-plus-repo.md --- 1. Log in to [MyF5 Customer Portal](https://account.f5.com/myf5/) and download diff --git a/content/includes/agent/installation/plus/plus-amazon-linux.md b/content/includes/agent/installation/plus/plus-amazon-linux.md index 5feb28bbe..19e9bc930 100644 --- a/content/includes/agent/installation/plus/plus-amazon-linux.md +++ b/content/includes/agent/installation/plus/plus-amazon-linux.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/install-from-plus-repo.md - - content/nginx-one/agent/install-upgrade/install-from-plus-repo.md + - content/nginx-one-console/agent/install-upgrade/install-from-plus-repo.md --- 1. Create the `/etc/ssl/nginx` directory: diff --git a/content/includes/agent/installation/plus/plus-debian.md b/content/includes/agent/installation/plus/plus-debian.md index ada38bda3..7c0179b21 100644 --- a/content/includes/agent/installation/plus/plus-debian.md +++ b/content/includes/agent/installation/plus/plus-debian.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/install-from-plus-repo.md - - content/nginx-one/agent/install-upgrade/install-from-plus-repo.md + - content/nginx-one-console/agent/install-upgrade/install-from-plus-repo.md --- 1. Create the `/etc/ssl/nginx` directory: diff --git a/content/includes/agent/installation/plus/plus-freebsd.md b/content/includes/agent/installation/plus/plus-freebsd.md index 3aff20ec5..e0200a63b 100644 --- a/content/includes/agent/installation/plus/plus-freebsd.md +++ b/content/includes/agent/installation/plus/plus-freebsd.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/install-from-plus-repo.md - - content/nginx-one/agent/install-upgrade/install-from-plus-repo.md + - content/nginx-one-console/agent/install-upgrade/install-from-plus-repo.md --- 1. Create the `/etc/ssl/nginx` directory: diff --git a/content/includes/agent/installation/plus/plus-rhel.md b/content/includes/agent/installation/plus/plus-rhel.md index 3b3deaf2b..73decc142 100644 --- a/content/includes/agent/installation/plus/plus-rhel.md +++ b/content/includes/agent/installation/plus/plus-rhel.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/install-from-plus-repo.md - - content/nginx-one/agent/install-upgrade/install-from-plus-repo.md + - content/nginx-one-console/agent/install-upgrade/install-from-plus-repo.md --- 1. Create the `/etc/ssl/nginx` directory: diff --git a/content/includes/agent/installation/plus/plus-sles.md b/content/includes/agent/installation/plus/plus-sles.md index bf25d69d1..514d7a558 100644 --- a/content/includes/agent/installation/plus/plus-sles.md +++ b/content/includes/agent/installation/plus/plus-sles.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/install-from-plus-repo.md - - content/nginx-one/agent/install-upgrade/install-from-plus-repo.md + - content/nginx-one-console/agent/install-upgrade/install-from-plus-repo.md --- 1. Create the `/etc/ssl/nginx` directory: diff --git a/content/includes/agent/installation/plus/plus-ubuntu.md b/content/includes/agent/installation/plus/plus-ubuntu.md index b2a0e1ca8..a6276a15d 100644 --- a/content/includes/agent/installation/plus/plus-ubuntu.md +++ b/content/includes/agent/installation/plus/plus-ubuntu.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/install-from-plus-repo.md - - content/nginx-one/agent/install-upgrade/install-from-plus-repo.md + - content/nginx-one-console/agent/install-upgrade/install-from-plus-repo.md --- 1. Create the `/etc/ssl/nginx` directory: diff --git a/content/includes/agent/installation/prerequisites.md b/content/includes/agent/installation/prerequisites.md index 18ee19108..9efc6a886 100644 --- a/content/includes/agent/installation/prerequisites.md +++ b/content/includes/agent/installation/prerequisites.md @@ -3,10 +3,10 @@ files: - content/agent/install-upgrade/install-from-github.md - content/agent/install-upgrade/install-from-oss-repo.md - content/agent/install-upgrade/install-from-plus-repo.md - - content/nginx-one/agent/install-upgrade/install-from-oss-repo.md - - content/nginx-one/agent/install-upgrade/install-from-plus-repo.md + - content/nginx-one-console/agent/install-upgrade/install-from-oss-repo.md + - content/nginx-one-console/agent/install-upgrade/install-from-plus-repo.md --- -- You must use one of the [supported operating system and architectures]({{< ref "/nginx-one/agent/overview/tech-specs.md#supported-distributions" >}}) +- You must use one of the [supported operating system and architectures]({{< ref "/nginx-one-console/agent/overview/tech-specs.md#supported-distributions" >}}) - The user running the NGINX Agent installation must have the same privileges as the main NGINX process. We recommend **not** running NGINX or NGINX Agent as the root user. \ No newline at end of file diff --git a/content/includes/agent/installation/start-stop-agent.md b/content/includes/agent/installation/start-stop-agent.md index e81a9219b..2cc0e37cf 100644 --- a/content/includes/agent/installation/start-stop-agent.md +++ b/content/includes/agent/installation/start-stop-agent.md @@ -3,8 +3,8 @@ files: - content/agent/install-upgrade/install-from-github.md - content/agent/install-upgrade/install-from-oss-repo.md - content/agent/install-upgrade/install-from-plus-repo.md - - content/nginx-one/agent/install-upgrade/install-from-oss-repo.md - - content/nginx-one/agent/install-upgrade/install-from-plus-repo.md + - content/nginx-one-console/agent/install-upgrade/install-from-oss-repo.md + - content/nginx-one-console/agent/install-upgrade/install-from-plus-repo.md --- To start NGINX Agent on `systemd` systems, run the following command: diff --git a/content/includes/agent/installation/uninstall/uninstall-alpine.md b/content/includes/agent/installation/uninstall/uninstall-alpine.md index 52abc96ee..1d8d5019c 100644 --- a/content/includes/agent/installation/uninstall/uninstall-alpine.md +++ b/content/includes/agent/installation/uninstall/uninstall-alpine.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/uninstall.md - - content/nginx-one/agent/install-upgrade/uninstall.md + - content/nginx-one-console/agent/install-upgrade/uninstall.md --- Complete the following steps on each host where you've installed NGINX agent: diff --git a/content/includes/agent/installation/uninstall/uninstall-amazon-linux.md b/content/includes/agent/installation/uninstall/uninstall-amazon-linux.md index f7223c7f2..95216546b 100644 --- a/content/includes/agent/installation/uninstall/uninstall-amazon-linux.md +++ b/content/includes/agent/installation/uninstall/uninstall-amazon-linux.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/uninstall.md - - content/nginx-one/agent/install-upgrade/uninstall.md + - content/nginx-one-console/agent/install-upgrade/uninstall.md --- Complete the following steps on each host where you've installed NGINX agent: diff --git a/content/includes/agent/installation/uninstall/uninstall-debian.md b/content/includes/agent/installation/uninstall/uninstall-debian.md index 899fc2e78..1eabb8807 100644 --- a/content/includes/agent/installation/uninstall/uninstall-debian.md +++ b/content/includes/agent/installation/uninstall/uninstall-debian.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/uninstall.md - - content/nginx-one/agent/install-upgrade/uninstall.md + - content/nginx-one-console/agent/install-upgrade/uninstall.md --- Complete the following steps on each host where you've installed NGINX Agent: diff --git a/content/includes/agent/installation/uninstall/uninstall-freebsd.md b/content/includes/agent/installation/uninstall/uninstall-freebsd.md index bd35a70e9..c2b3583b7 100644 --- a/content/includes/agent/installation/uninstall/uninstall-freebsd.md +++ b/content/includes/agent/installation/uninstall/uninstall-freebsd.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/uninstall.md - - content/nginx-one/agent/install-upgrade/uninstall.md + - content/nginx-one-console/agent/install-upgrade/uninstall.md --- Complete the following steps on each host where you've installed NGINX agent: diff --git a/content/includes/agent/installation/uninstall/uninstall-rhel.md b/content/includes/agent/installation/uninstall/uninstall-rhel.md index ab77b04c1..2d1909edc 100644 --- a/content/includes/agent/installation/uninstall/uninstall-rhel.md +++ b/content/includes/agent/installation/uninstall/uninstall-rhel.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/uninstall.md - - content/nginx-one/agent/install-upgrade/uninstall.md + - content/nginx-one-console/agent/install-upgrade/uninstall.md --- Complete the following steps on each host where you've installed NGINX Agent: diff --git a/content/includes/agent/installation/uninstall/uninstall-sles.md b/content/includes/agent/installation/uninstall/uninstall-sles.md index 0dc962365..24832bf6b 100644 --- a/content/includes/agent/installation/uninstall/uninstall-sles.md +++ b/content/includes/agent/installation/uninstall/uninstall-sles.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/uninstall.md - - content/nginx-one/agent/install-upgrade/uninstall.md + - content/nginx-one-console/agent/install-upgrade/uninstall.md --- Complete the following steps on each host where you've installed NGINX Agent: diff --git a/content/includes/agent/installation/uninstall/uninstall-ubuntu.md b/content/includes/agent/installation/uninstall/uninstall-ubuntu.md index 899fc2e78..1eabb8807 100644 --- a/content/includes/agent/installation/uninstall/uninstall-ubuntu.md +++ b/content/includes/agent/installation/uninstall/uninstall-ubuntu.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/uninstall.md - - content/nginx-one/agent/install-upgrade/uninstall.md + - content/nginx-one-console/agent/install-upgrade/uninstall.md --- Complete the following steps on each host where you've installed NGINX Agent: diff --git a/content/includes/agent/installation/update-container.md b/content/includes/agent/installation/update-container.md index 13caccf40..8cc610c44 100644 --- a/content/includes/agent/installation/update-container.md +++ b/content/includes/agent/installation/update-container.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/update.md - - content/nginx-one/agent/install-upgrade/update.md + - content/nginx-one-console/agent/install-upgrade/update.md --- To migrate NGINX Agent containers, we provide a script to convert NGINX Agent v2 config files to NGINX Agent v3 config files: [NGINX Agent Config Upgrade Script](https://github.com/nginx/agent/blob/v3/scripts/packages/upgrade-agent-config.sh) @@ -14,7 +14,7 @@ wget https://raw.githubusercontent.com/nginx/agent/refs/heads/main/scripts/packa ``` If your NGINX Agent container was previously a member of a Config Sync Group, then your NGINX Agent config must be manually updated to add the Config Sync Group label. -See [Add Config Sync Group]({{< ref "/nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups.md" >}}) for more information. +See [Add Config Sync Group]({{< ref "/nginx-one-console/nginx-configs/config-sync-groups/manage-config-sync-groups.md" >}}) for more information. ### Rolling back from NGINX Agent v3 to v2 diff --git a/content/includes/agent/installation/update.md b/content/includes/agent/installation/update.md index ba2965b34..e2232b9a4 100644 --- a/content/includes/agent/installation/update.md +++ b/content/includes/agent/installation/update.md @@ -1,7 +1,7 @@ --- files: - content/agent/install-upgrade/update.md - - content/nginx-one/agent/install-upgrade/update.md + - content/nginx-one-console/agent/install-upgrade/update.md --- diff --git a/content/includes/agent/installation/verify-agent.md b/content/includes/agent/installation/verify-agent.md index 0b3fdbdcc..b5c3b025e 100644 --- a/content/includes/agent/installation/verify-agent.md +++ b/content/includes/agent/installation/verify-agent.md @@ -3,8 +3,8 @@ files: - content/agent/install-upgrade/install-from-github.md - content/agent/install-upgrade/install-from-oss-repo.md - content/agent/install-upgrade/install-from-plus-repo.md - - content/nginx-one/agent/install-upgrade/install-from-oss-repo.md - - content/nginx-one/agent/install-upgrade/install-from-plus-repo.md + - content/nginx-one-console/agent/install-upgrade/install-from-oss-repo.md + - content/nginx-one-console/agent/install-upgrade/install-from-plus-repo.md --- Once you have installed NGINX Agent, you can verify that it is running with the diff --git a/content/includes/agent/tech-specs.md b/content/includes/agent/tech-specs.md index 83553622c..3c8a692da 100644 --- a/content/includes/agent/tech-specs.md +++ b/content/includes/agent/tech-specs.md @@ -1,7 +1,7 @@ --- files: - content/agent/tech-specs.md - - content/nginx-one/agent/overview/tech-specs.md + - content/nginx-one-console/agent/overview/tech-specs.md --- NGINX Agent is designed to operate efficiently on any system that meets the standard diff --git a/content/includes/agent/v3-available.md b/content/includes/agent/v3-available.md index 432cf44dd..fa06bcd51 100644 --- a/content/includes/agent/v3-available.md +++ b/content/includes/agent/v3-available.md @@ -1,11 +1,11 @@ --- files: - - content/nginx-one/agent/overview/about.md - - content/nginx-one/agent/changelog.md + - content/nginx-one-console/agent/overview/about.md + - content/nginx-one-console/agent/changelog.md --- {{}} NGINX Agent v3.0 is a major release that introduces new features and enhancements. -Visit our [Update]({{< ref "/nginx-one/agent/install-upgrade/update.md" >}}) guide to install the latest version in your environment. +Visit our [Update]({{< ref "/nginx-one-console/agent/install-upgrade/update.md" >}}) guide to install the latest version in your environment. {{}} \ No newline at end of file diff --git a/content/includes/config-snippets/enable-nplus-api-dashboard.md b/content/includes/config-snippets/enable-nplus-api-dashboard.md index d79b586d1..a3a4cfdbe 100644 --- a/content/includes/config-snippets/enable-nplus-api-dashboard.md +++ b/content/includes/config-snippets/enable-nplus-api-dashboard.md @@ -1,6 +1,6 @@ --- files: -- content/nginx-one/workshops/lab5/upgrade-nginx-plus-to-latest-version.md +- content/nginx-one-console/workshops/lab5/upgrade-nginx-plus-to-latest-version.md - content/includes/use-cases/monitoring/enable-nginx-plus-api.md --- diff --git a/content/includes/installation/add-ports-agent-selinux.md b/content/includes/installation/add-ports-agent-selinux.md index 60d67313d..43019a234 100644 --- a/content/includes/installation/add-ports-agent-selinux.md +++ b/content/includes/installation/add-ports-agent-selinux.md @@ -1,6 +1,6 @@ --- files: - - content/nginx-one/agent/configure-instances/configure-selinux.md + - content/nginx-one-console/agent/configure-instances/configure-selinux.md - content/nim/system-configuration/configure-selinux.md - content/nms/nginx-agent/install-nginx-agent.md --- diff --git a/content/includes/installation/enable-agent-selinux.md b/content/includes/installation/enable-agent-selinux.md index 0175336f8..9aba4e12d 100644 --- a/content/includes/installation/enable-agent-selinux.md +++ b/content/includes/installation/enable-agent-selinux.md @@ -1,6 +1,6 @@ --- files: - - content/nginx-one/agent/configure-instances/configure-selinux.md + - content/nginx-one-console/agent/configure-instances/configure-selinux.md - content/nim/system-configuration/configure-selinux.md - content/nms/nginx-agent/install-nginx-agent.md --- diff --git a/content/includes/licensing-and-reporting/deploy-jwt-with-csgs.md b/content/includes/licensing-and-reporting/deploy-jwt-with-csgs.md index 0b279a83e..31362eb64 100644 --- a/content/includes/licensing-and-reporting/deploy-jwt-with-csgs.md +++ b/content/includes/licensing-and-reporting/deploy-jwt-with-csgs.md @@ -6,7 +6,7 @@ file: {{}} Before you deploy with a Config Sync Group, you need to create one in the NGINX One Console. -If you haven’t created a group yet, see [Manage Config Sync Groups]({{< ref "/nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups.md" >}}) for instructions. +If you haven’t created a group yet, see [Manage Config Sync Groups]({{< ref "/nginx-one-console/nginx-configs/config-sync-groups/manage-config-sync-groups.md" >}}) for instructions. {{}} 1. In the NGINX One Console, go to **Manage > Config Sync Groups**, then select your group. diff --git a/content/includes/licensing-and-reporting/download-jwt-from-myf5.md b/content/includes/licensing-and-reporting/download-jwt-from-myf5.md index 339d2ee54..a4338a1d6 100644 --- a/content/includes/licensing-and-reporting/download-jwt-from-myf5.md +++ b/content/includes/licensing-and-reporting/download-jwt-from-myf5.md @@ -4,7 +4,7 @@ files: - content/includes/use-cases/credential-download-instructions.md - content/nap-waf/v5/admin-guide/install.md - content/nginx/admin-guide/installing-nginx/installing-nginx-plus.md -- content/nginx-one/connect-instances/connect-nginx-plus-container-images-to-nginx-one.md +- content/nginx-one-console/connect-instances/connect-nginx-plus-container-images-to-nginx-one.md - content/nim/admin-guide/add-license.md - content/nim/deploy/docker/deploy-nginx-plus-and-agent-docker.md - content/nim/disconnected/add-license-disconnected-deployment.md diff --git a/content/includes/ngf/installation/deploy-ngf-crds.md b/content/includes/ngf/installation/deploy-ngf-crds.md index 14161e06c..db4a840db 100644 --- a/content/includes/ngf/installation/deploy-ngf-crds.md +++ b/content/includes/ngf/installation/deploy-ngf-crds.md @@ -2,7 +2,7 @@ nd-docs: "DOCS-000" files: - content/ngf/install/manifests.md -- content/nginx-one/ngf/add-ngf-manifests.md +- content/nginx-one-console/ngf/add-ngf-manifests.md --- #### Stable release diff --git a/content/includes/ngf/installation/deploy-ngf-manifests.md b/content/includes/ngf/installation/deploy-ngf-manifests.md index 17183bbad..bac1f5293 100644 --- a/content/includes/ngf/installation/deploy-ngf-manifests.md +++ b/content/includes/ngf/installation/deploy-ngf-manifests.md @@ -2,7 +2,7 @@ nd-docs: "DOCS-000" files: - content/ngf/install/manifests.md -- content/nginx-one/ngf/add-ngf-manifests.md +- content/nginx-one-console/ngf/add-ngf-manifests.md --- {{< call-out "note" >}} By default, NGINX Gateway Fabric is installed in the **nginx-gateway** namespace. You can deploy in another namespace by modifying the manifest files. {{< /call-out >}} diff --git a/content/includes/ngf/installation/install-manifests-prereqs.md b/content/includes/ngf/installation/install-manifests-prereqs.md index 0385a4399..3b22598dc 100644 --- a/content/includes/ngf/installation/install-manifests-prereqs.md +++ b/content/includes/ngf/installation/install-manifests-prereqs.md @@ -2,7 +2,7 @@ nd-docs: "DOCS-000" files: - content/ngf/install/manifests.md -- content/nginx-one/ngf/add-ngf-manifests.md +- content/nginx-one-console/ngf/add-ngf-manifests.md --- To complete this guide, you'll need to install: diff --git a/content/includes/nginx-one/add-file/edit-config-tip.md b/content/includes/nginx-one-console/add-file/edit-config-tip.md similarity index 100% rename from content/includes/nginx-one/add-file/edit-config-tip.md rename to content/includes/nginx-one-console/add-file/edit-config-tip.md diff --git a/content/includes/nginx-one/add-file/existing-ssl-bundle.md b/content/includes/nginx-one-console/add-file/existing-ssl-bundle.md similarity index 89% rename from content/includes/nginx-one/add-file/existing-ssl-bundle.md rename to content/includes/nginx-one-console/add-file/existing-ssl-bundle.md index e929e9d87..1284dab66 100644 --- a/content/includes/nginx-one/add-file/existing-ssl-bundle.md +++ b/content/includes/nginx-one-console/add-file/existing-ssl-bundle.md @@ -1,7 +1,7 @@ --- --- -With this option, you can incorporate [Managed certificates]({{< ref "/nginx-one/nginx-configs/certificates/manage-certificates.md#managed-and-unmanaged-certificates" >}}). +With this option, you can incorporate [Managed certificates]({{< ref "/nginx-one-console/nginx-configs/certificates/manage-certificates.md#managed-and-unmanaged-certificates" >}}). In the **Choose Certificate** drop-down, select the managed certificate of your choice, and select **Add**. You can then: 1. Review details of the certificate. The next steps depend on whether the certificate is a CA bundle or a certificate / key pair. diff --git a/content/includes/nginx-one/add-file/new-ssl-bundle.md b/content/includes/nginx-one-console/add-file/new-ssl-bundle.md similarity index 100% rename from content/includes/nginx-one/add-file/new-ssl-bundle.md rename to content/includes/nginx-one-console/add-file/new-ssl-bundle.md diff --git a/content/includes/nginx-one/add-file/overview.md b/content/includes/nginx-one-console/add-file/overview.md similarity index 100% rename from content/includes/nginx-one/add-file/overview.md rename to content/includes/nginx-one-console/add-file/overview.md diff --git a/content/includes/nginx-one/alert-labels.md b/content/includes/nginx-one-console/alert-labels.md similarity index 93% rename from content/includes/nginx-one/alert-labels.md rename to content/includes/nginx-one-console/alert-labels.md index e304b8f6c..f24faf179 100644 --- a/content/includes/nginx-one/alert-labels.md +++ b/content/includes/nginx-one-console/alert-labels.md @@ -1,11 +1,11 @@ --- files: - - content/nginx-one/secure-your-fleet/set-up-security-alerts.md - - content/nginx-one/glossary.md + - content/nginx-one-console/secure-your-fleet/set-up-security-alerts.md + - content/nginx-one-console/glossary.md --- -You can configure a variety of NGINX alerts in the F5 Distributed Cloud. If you have access to the [F5 Distributed Cloud]({{< ref "/nginx-one/getting-started.md#confirm-access-to-the-f5-distributed-cloud" >}}), log in and select the **Audit Logs & Alerts** tile. +You can configure a variety of NGINX alerts in the F5 Distributed Cloud. If you have access to the [F5 Distributed Cloud]({{< ref "/nginx-one-console/getting-started.md#confirm-access-to-the-f5-distributed-cloud" >}}), log in and select the **Audit Logs & Alerts** tile. Go to **Notifications > Alerts**. Select the gear icon and select **Alert Name > Active Alerts**. You may see one or more of the following alerts in the **Audit Logs & Alerts** Console. diff --git a/content/includes/nginx-one/cloud-access-nginx.md b/content/includes/nginx-one-console/cloud-access-nginx.md similarity index 87% rename from content/includes/nginx-one/cloud-access-nginx.md rename to content/includes/nginx-one-console/cloud-access-nginx.md index ead892c9d..9da7904d6 100644 --- a/content/includes/nginx-one/cloud-access-nginx.md +++ b/content/includes/nginx-one-console/cloud-access-nginx.md @@ -1,6 +1,6 @@ --- files: - - content/nginx-one/getting-started.md + - content/nginx-one-console/getting-started.md --- 1. Go to `https://.console.ves.volterra.io/` to access F5 Distributed Cloud, and sign in. diff --git a/content/includes/nginx-one/cloud-access.md b/content/includes/nginx-one-console/cloud-access.md similarity index 85% rename from content/includes/nginx-one/cloud-access.md rename to content/includes/nginx-one-console/cloud-access.md index a92c1380c..64ba84be5 100644 --- a/content/includes/nginx-one/cloud-access.md +++ b/content/includes/nginx-one-console/cloud-access.md @@ -1,8 +1,8 @@ --- files: - - content/nginx-one/secure-your-fleet/set-up-security-alerts.md - - content/nginx-one/getting-started.md - - content/nginx-one/workshops/lab1/getting-started-with-nginx-one-console.md + - content/nginx-one-console/secure-your-fleet/set-up-security-alerts.md + - content/nginx-one-console/getting-started.md + - content/nginx-one-console/workshops/lab1/getting-started-with-nginx-one-console.md --- Confirm that an F5 Distributed Cloud tenant has been provisioned for you. To do so: diff --git a/content/includes/nginx-one/conf/nginx-agent-conf.md b/content/includes/nginx-one-console/conf/nginx-agent-conf.md similarity index 74% rename from content/includes/nginx-one/conf/nginx-agent-conf.md rename to content/includes/nginx-one-console/conf/nginx-agent-conf.md index 0c2266273..aa3eec3b4 100644 --- a/content/includes/nginx-one/conf/nginx-agent-conf.md +++ b/content/includes/nginx-one-console/conf/nginx-agent-conf.md @@ -1,7 +1,7 @@ --- files: - - content/nginx-one/getting-started.md - - content/nginx-one/agent/containers/run-agent-container.md + - content/nginx-one-console/getting-started.md + - content/nginx-one-console/agent/containers/run-agent-container.md --- ```yaml diff --git a/content/includes/nginx-one/how-to/add-instance.md b/content/includes/nginx-one-console/how-to/add-instance.md similarity index 75% rename from content/includes/nginx-one/how-to/add-instance.md rename to content/includes/nginx-one-console/how-to/add-instance.md index 998a101d7..50fbdda68 100644 --- a/content/includes/nginx-one/how-to/add-instance.md +++ b/content/includes/nginx-one-console/how-to/add-instance.md @@ -1,7 +1,7 @@ --- files: - - content/nginx-one/connect-instances/add-instance.md - - content/nginx-one/getting-started.md + - content/nginx-one-console/connect-instances/add-instance.md + - content/nginx-one-console/getting-started.md --- You can add an instance to NGINX One Console in the following ways: @@ -16,7 +16,7 @@ In either case, NGINX One Console gives you a choice for data plane keys: NGINX One Console takes the option you use, and adds the data plane key to a command that you'd use to register your target instance. You should see the command in the **Add Instance** screen in the console. -Connect to the host where your NGINX instance is running. Run the provided command to [install NGINX Agent]({{< ref "/nginx-one/getting-started#install-nginx-agent" >}}) dependencies and packages on that host. +Connect to the host where your NGINX instance is running. Run the provided command to [install NGINX Agent]({{< ref "/nginx-one-console/getting-started#install-nginx-agent" >}}) dependencies and packages on that host. ```bash curl https://agent.connect.nginx.com/nginx-agent/install | DATA_PLANE_KEY="" sh -s -- -y diff --git a/content/includes/nginx-one/how-to/generate-data-plane-key.md b/content/includes/nginx-one-console/how-to/generate-data-plane-key.md similarity index 52% rename from content/includes/nginx-one/how-to/generate-data-plane-key.md rename to content/includes/nginx-one-console/how-to/generate-data-plane-key.md index ced4797e0..d921a7af5 100644 --- a/content/includes/nginx-one/how-to/generate-data-plane-key.md +++ b/content/includes/nginx-one-console/how-to/generate-data-plane-key.md @@ -1,10 +1,10 @@ --- files: - - content/nginx-one/secure-your-fleet/set-up-security-alerts.md - - content/nginx-one/getting-started.md - - content/nginx-one/ngf/add-nic.md - - content/nginx-one/ngf/add-ngf-helm.md - - content/nginx-one/ngf/add-ngf-manifests.md + - content/nginx-one-console/secure-your-fleet/set-up-security-alerts.md + - content/nginx-one-console/getting-started.md + - content/nginx-one-console/ngf/add-nic.md + - content/nginx-one-console/ngf/add-ngf-helm.md + - content/nginx-one-console/ngf/add-ngf-manifests.md --- A data plane key is a security token that ensures only trusted NGINX instances can register and communicate with NGINX One. @@ -17,7 +17,7 @@ To generate a data plane key, select **Manage > Instances > Add Instance**: {{}} Data plane keys are displayed only once and cannot be retrieved later. Be sure to copy and store this key securely. -Data plane keys expire after one year. You can change this expiration date later by [editing the key]({{< ref "nginx-one/connect-instances/create-manage-data-plane-keys.md#change-expiration-date" >}}). If you [revoke a data plane key]({{< ref "nginx-one/connect-instances/create-manage-data-plane-keys.md#revoke-data-plane-key" >}}) you disconnect all instances registered with that key. +Data plane keys expire after one year. You can change this expiration date later by [editing the key]({{< ref "/nginx-one-console/connect-instances/create-manage-data-plane-keys.md#change-expiration-date" >}}). If you [revoke a data plane key]({{< ref "/nginx-one-console/connect-instances/create-manage-data-plane-keys.md#revoke-data-plane-key" >}}) you disconnect all instances registered with that key. {{}} -For more options associated with data plane keys, see [Create and manage data plane keys]({{< ref "/nginx-one/connect-instances/create-manage-data-plane-keys.md" >}}). +For more options associated with data plane keys, see [Create and manage data plane keys]({{< ref "/nginx-one-console/connect-instances/create-manage-data-plane-keys.md" >}}). diff --git a/content/includes/nginx-one/how-to/install-nginx-agent.md b/content/includes/nginx-one-console/how-to/install-nginx-agent.md similarity index 91% rename from content/includes/nginx-one/how-to/install-nginx-agent.md rename to content/includes/nginx-one-console/how-to/install-nginx-agent.md index 090b6f300..743b7944c 100644 --- a/content/includes/nginx-one/how-to/install-nginx-agent.md +++ b/content/includes/nginx-one-console/how-to/install-nginx-agent.md @@ -1,7 +1,7 @@ --- files: - - content/nginx-one/secure-your-fleet/set-up-security-alerts.md - - content/nginx-one/getting-started.md + - content/nginx-one-console/secure-your-fleet/set-up-security-alerts.md + - content/nginx-one-console/getting-started.md --- After entering your data plane key, you'll see a `curl` command to install NGINX Agent, similar to the one below. Copy and run this command on each NGINX instance. Once installed, NGINX Agent typically registers with NGINX One within a few seconds. diff --git a/content/includes/nginx-one/how-to/k8s-secret-dp-key.md b/content/includes/nginx-one-console/how-to/k8s-secret-dp-key.md similarity index 82% rename from content/includes/nginx-one/how-to/k8s-secret-dp-key.md rename to content/includes/nginx-one-console/how-to/k8s-secret-dp-key.md index bb9db5f75..400c11af5 100644 --- a/content/includes/nginx-one/how-to/k8s-secret-dp-key.md +++ b/content/includes/nginx-one-console/how-to/k8s-secret-dp-key.md @@ -1,8 +1,8 @@ --- nd-docs: "DOCS-000" files: -- content/nginx-one/k8s/add-ngf-manifests.md -- content/nginx-one/k8s/add-ngf-helm.md +- content/nginx-one-console/k8s/add-ngf-manifests.md +- content/nginx-one-console/k8s/add-ngf-helm.md --- To create a Kubernetes secret, you'll need: diff --git a/content/includes/nginx-one/how-to/ngf-troubleshooting.md b/content/includes/nginx-one-console/how-to/ngf-troubleshooting.md similarity index 83% rename from content/includes/nginx-one/how-to/ngf-troubleshooting.md rename to content/includes/nginx-one-console/how-to/ngf-troubleshooting.md index 52a9db7a0..4ef8cab65 100644 --- a/content/includes/nginx-one/how-to/ngf-troubleshooting.md +++ b/content/includes/nginx-one-console/how-to/ngf-troubleshooting.md @@ -1,8 +1,8 @@ --- nd-docs: "DOCS-000" files: -- content/nginx-one/k8s/add-ngf-manifests.md -- content/nginx-one/k8s/add-ngf-helm.md +- content/nginx-one-console/k8s/add-ngf-manifests.md +- content/nginx-one-console/k8s/add-ngf-helm.md --- If you encounter issues connecting your instances to NGINX One Console, try the following commands: diff --git a/content/includes/nginx-one/how-to/verify-connection.md b/content/includes/nginx-one-console/how-to/verify-connection.md similarity index 85% rename from content/includes/nginx-one/how-to/verify-connection.md rename to content/includes/nginx-one-console/how-to/verify-connection.md index 189176a6d..ce4510a88 100644 --- a/content/includes/nginx-one/how-to/verify-connection.md +++ b/content/includes/nginx-one-console/how-to/verify-connection.md @@ -1,8 +1,8 @@ --- nd-docs: "DOCS-000" files: -- content/nginx-one/k8s/add-ngf-manifests.md -- content/nginx-one/k8s/add-ngf-helm.md +- content/nginx-one-console/k8s/add-ngf-manifests.md +- content/nginx-one-console/k8s/add-ngf-helm.md --- After deploying NGINX Gateway Fabric with NGINX Agent, you can verify the connection to NGINX One Console. diff --git a/content/includes/nginx-one/install-nginx.md b/content/includes/nginx-one-console/install-nginx.md similarity index 79% rename from content/includes/nginx-one/install-nginx.md rename to content/includes/nginx-one-console/install-nginx.md index e00419a29..41c8d6a37 100644 --- a/content/includes/nginx-one/install-nginx.md +++ b/content/includes/nginx-one-console/install-nginx.md @@ -1,7 +1,7 @@ --- files: - - content/nginx-one/secure-your-fleet/set-up-security-alerts.md - - content/nginx-one/getting-started.md + - content/nginx-one-console/secure-your-fleet/set-up-security-alerts.md + - content/nginx-one-console/getting-started.md --- If you need to set up an instance of NGINX, you can do so in one of the following ways: diff --git a/content/includes/nginx-one/staged-config-overview.md b/content/includes/nginx-one-console/staged-config-overview.md similarity index 82% rename from content/includes/nginx-one/staged-config-overview.md rename to content/includes/nginx-one-console/staged-config-overview.md index f47aec5d5..c7d13ee7c 100644 --- a/content/includes/nginx-one/staged-config-overview.md +++ b/content/includes/nginx-one-console/staged-config-overview.md @@ -1,8 +1,8 @@ --- nd-docs: DOCS-000 files: - - content/nginx-one/how-to/staged-configs/add-staged-config.md - - content/nginx-one/how-to/staged-configs/edit-staged-config.md + - content/nginx-one-console/how-to/staged-configs/add-staged-config.md + - content/nginx-one-console/how-to/staged-configs/edit-staged-config.md --- It takes time to set up NGINX configuration files. Staged Configurations can help. They work like a draft that uses the features of NGINX One Console. The Staged Configuration does not have to be valid. diff --git a/content/includes/nginx-one-console/workshops/xc-account.md b/content/includes/nginx-one-console/workshops/xc-account.md new file mode 100644 index 000000000..27dbc0b5d --- /dev/null +++ b/content/includes/nginx-one-console/workshops/xc-account.md @@ -0,0 +1,9 @@ +--- +files: + - content/nginx-one-console/workshops/lab2/run-workshop-components-with-docker.md + - content/nginx-one-console/workshops/lab3/explore-nginx-one-console-features.md + - content/nginx-one-console/workshops/lab4/config-sync-groups.md + - content/nginx-one-console/workshops/lab5/upgrade-nginx-plus-to-latest-version.md +--- + +All labs require an **F5 Distributed Cloud (XC) account** with NGINX One enabled. If you don’t have an account or need to verify access, follow the steps in [Lab 1: Before you begin]({{< ref "/nginx-one-console/workshops/lab1/getting-started-with-nginx-one-console.md#before-you-begin" >}}). \ No newline at end of file diff --git a/content/includes/nginx-one/workshops/xc-account.md b/content/includes/nginx-one/workshops/xc-account.md deleted file mode 100644 index f0d3ad69f..000000000 --- a/content/includes/nginx-one/workshops/xc-account.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -files: - - content/nginx-one/workshops/lab2/run-workshop-components-with-docker.md - - content/nginx-one/workshops/lab3/explore-nginx-one-console-features.md - - content/nginx-one/workshops/lab4/config-sync-groups.md - - content/nginx-one/workshops/lab5/upgrade-nginx-plus-to-latest-version.md ---- - -All labs require an **F5 Distributed Cloud (XC) account** with NGINX One enabled. If you don’t have an account or need to verify access, follow the steps in [Lab 1: Before you begin]({{< ref "nginx-one/workshops/lab1/getting-started-with-nginx-one-console.md#before-you-begin" >}}). \ No newline at end of file diff --git a/content/includes/security/rbac-intro.md b/content/includes/security/rbac-intro.md index e45dce9c5..306646790 100644 --- a/content/includes/security/rbac-intro.md +++ b/content/includes/security/rbac-intro.md @@ -1,6 +1,6 @@ --- files: - - content/nginx-one/rbac/overview.md + - content/nginx-one-console/rbac/overview.md - content/nim/admin-guide/rbac/overview-rbac.md nd-docs: DOCS-000 --- diff --git a/content/includes/use-cases/monitoring/enable-nginx-oss-stub-status.md b/content/includes/use-cases/monitoring/enable-nginx-oss-stub-status.md index 1caa86fc7..1af06ff00 100644 --- a/content/includes/use-cases/monitoring/enable-nginx-oss-stub-status.md +++ b/content/includes/use-cases/monitoring/enable-nginx-oss-stub-status.md @@ -1,7 +1,7 @@ --- files: - content/nim/monitoring/overview-metrics.md - - content/nginx-one/getting-started.md + - content/nginx-one-console/getting-started.md --- To collect basic metrics about server activity for NGINX Open Source, add the following to your NGINX configuration file: diff --git a/content/includes/use-cases/monitoring/enable-nginx-plus-api-with-config-sync-group.md b/content/includes/use-cases/monitoring/enable-nginx-plus-api-with-config-sync-group.md index e728c8fc5..2ff20de2b 100644 --- a/content/includes/use-cases/monitoring/enable-nginx-plus-api-with-config-sync-group.md +++ b/content/includes/use-cases/monitoring/enable-nginx-plus-api-with-config-sync-group.md @@ -1,7 +1,7 @@ --- files: -- content/nginx-one/workshops/lab5/upgrade-nginx-plus-to-latest-version.md -- content/nginx-one/nginx-configs/metrics/enable-metrics.md +- content/nginx-one-console/workshops/lab5/upgrade-nginx-plus-to-latest-version.md +- content/nginx-one-console/nginx-configs/metrics/enable-metrics.md --- 1. In the NGINX One Console, select **Manage > Config Sync Groups**, then pick your config sync group's name. diff --git a/content/includes/use-cases/monitoring/enable-nginx-plus-api.md b/content/includes/use-cases/monitoring/enable-nginx-plus-api.md index 35dcc6385..acd462f7d 100644 --- a/content/includes/use-cases/monitoring/enable-nginx-plus-api.md +++ b/content/includes/use-cases/monitoring/enable-nginx-plus-api.md @@ -1,7 +1,7 @@ --- files: - content/nim/monitoring/overview-metrics.md - - content/nginx-one/getting-started.md + - content/nginx-one-console/getting-started.md --- To collect comprehensive metrics for NGINX Plus, including bytes streamed, information about upstream systems and caches, and counts of all HTTP status codes, add the following to your NGINX Plus configuration file, for example `/etc/nginx/nginx.conf` or an included file: diff --git a/content/includes/use-cases/monitoring/enable-nginx-plus-status-zone-limited.md b/content/includes/use-cases/monitoring/enable-nginx-plus-status-zone-limited.md index b80dad617..c3b5e92a1 100644 --- a/content/includes/use-cases/monitoring/enable-nginx-plus-status-zone-limited.md +++ b/content/includes/use-cases/monitoring/enable-nginx-plus-status-zone-limited.md @@ -1,6 +1,6 @@ --- files: - - content/nginx-one/nginx-configs/metrics/enable-metrics.md + - content/nginx-one-console/nginx-configs/metrics/enable-metrics.md --- To make NGINX Plus metrics available on the NGINX One Console, you must enable shared memory zones for the virtual servers being monitored. Shared memory zones store configuration and runtime state information shared across NGINX worker processes. diff --git a/content/includes/use-cases/monitoring/n1c-dashboard-overview.md b/content/includes/use-cases/monitoring/n1c-dashboard-overview.md index 32dc86dd4..fcdd58745 100644 --- a/content/includes/use-cases/monitoring/n1c-dashboard-overview.md +++ b/content/includes/use-cases/monitoring/n1c-dashboard-overview.md @@ -1,7 +1,7 @@ --- files: - - content/nginx-one/metrics/enable-metrics.md - - content/nginx-one/getting-started.md + - content/nginx-one-console/metrics/enable-metrics.md + - content/nginx-one-console/getting-started.md --- Navigating the dashboard: diff --git a/content/includes/workshops/nginx-one-env-variables.md b/content/includes/workshops/nginx-one-env-variables.md index 5cb348254..5660ee8e3 100644 --- a/content/includes/workshops/nginx-one-env-variables.md +++ b/content/includes/workshops/nginx-one-env-variables.md @@ -1,7 +1,7 @@ --- files: -- content/nginx-one/workshops/lab4/config-sync-groups.md -- content/nginx-one/workshops/lab5/upgrade-nginx-plus-to-r34.md +- content/nginx-one-console/workshops/lab4/config-sync-groups.md +- content/nginx-one-console/workshops/lab5/upgrade-nginx-plus-to-r34.md --- diff --git a/content/nginx-one/_index.md b/content/nginx-one-console/_index.md similarity index 92% rename from content/nginx-one/_index.md rename to content/nginx-one-console/_index.md index 3c12f1716..05ece2d60 100644 --- a/content/nginx-one/_index.md +++ b/content/nginx-one-console/_index.md @@ -1,7 +1,7 @@ --- title: F5 NGINX One Console nd-subtitle: Optimize, secure, and scale your modern apps -url: /nginx-one/ +url: /nginx-one-console/ nd-landing-page: true cascade: logo: "NGINX-One-product-icon.svg" @@ -30,13 +30,13 @@ F5 NGINX One Console makes it easy to manage NGINX instances across locations an {{}} Work with data plane keys, containers, and proxy servers {{}} - {{}} + {{}} Configure alerts that match your security policies {{}} - {{}} + {{}} Manage one instance or groups of instances. Monitor certificates. Set up metrics. {{}} - {{}} + {{}} Monitor deployments for CVEs and certificates {{}} {{}} @@ -45,7 +45,7 @@ F5 NGINX One Console makes it easy to manage NGINX instances across locations an {{}} - {{}} + {{}} Guided labs to help you secure, monitor, and scale your NGINX fleet with NGINX One Console. {{}} {{}} @@ -54,16 +54,16 @@ F5 NGINX One Console makes it easy to manage NGINX instances across locations an ### More information {{}} - {{}} + {{}} Set up security policies by instance and group {{}} - {{}} + {{}} Assign responsibilities with role-based access control {{}} - {{}} + {{}} Manage your NGINX fleet over REST {{}} - {{}} + {{}} Includes NGINX-specific security alert labels {{}} {{}} diff --git a/content/nginx-one/agent/_index.md b/content/nginx-one-console/agent/_index.md similarity index 78% rename from content/nginx-one/agent/_index.md rename to content/nginx-one-console/agent/_index.md index 159229def..a92a2d4f3 100644 --- a/content/nginx-one/agent/_index.md +++ b/content/nginx-one-console/agent/_index.md @@ -2,5 +2,5 @@ title: NGINX Agent description: Learn about NGINX Agent, its features, and how to install it. weight: 750 -url: /nginx-one/agent/ +url: /nginx-one-console/agent/ --- diff --git a/content/nginx-one/agent/changelog.md b/content/nginx-one-console/agent/changelog.md similarity index 86% rename from content/nginx-one/agent/changelog.md rename to content/nginx-one-console/agent/changelog.md index dc603dd71..8f465c775 100644 --- a/content/nginx-one/agent/changelog.md +++ b/content/nginx-one-console/agent/changelog.md @@ -1,7 +1,7 @@ --- title: Agent changelog toc: false -url: /nginx-one/agent/changelog +url: /nginx-one-console/agent/changelog weight: 1200 nd-docs: DOCS-1868 --- diff --git a/content/nginx-one/agent/community.md b/content/nginx-one-console/agent/community.md similarity index 100% rename from content/nginx-one/agent/community.md rename to content/nginx-one-console/agent/community.md diff --git a/content/nginx-one-console/agent/configure-instances/_index.md b/content/nginx-one-console/agent/configure-instances/_index.md new file mode 100644 index 000000000..89876f546 --- /dev/null +++ b/content/nginx-one-console/agent/configure-instances/_index.md @@ -0,0 +1,5 @@ +--- +title: "Configure instances" +weight: 400 +url: /nginx-one-console/agent/configure-instances/ +--- \ No newline at end of file diff --git a/content/nginx-one/agent/configure-instances/configuration-overview.md b/content/nginx-one-console/agent/configure-instances/configuration-overview.md similarity index 100% rename from content/nginx-one/agent/configure-instances/configuration-overview.md rename to content/nginx-one-console/agent/configure-instances/configuration-overview.md diff --git a/content/nginx-one/agent/configure-instances/configure-agent-features.md b/content/nginx-one-console/agent/configure-instances/configure-agent-features.md similarity index 96% rename from content/nginx-one/agent/configure-instances/configure-agent-features.md rename to content/nginx-one-console/agent/configure-instances/configure-agent-features.md index ea29b6e1e..29708c6a2 100644 --- a/content/nginx-one/agent/configure-instances/configure-agent-features.md +++ b/content/nginx-one-console/agent/configure-instances/configure-agent-features.md @@ -14,7 +14,7 @@ This guide describes the F5 NGINX Agent features, and how to enable and disable Before you start, make sure that you have: -- [NGINX Agent installed]({{< ref "/nginx-one/agent/install-upgrade/" >}}) in your system. +- [NGINX Agent installed]({{< ref "/nginx-one-console/agent/install-upgrade/" >}}) in your system. - Access to the NGINX Agent configuration file, CLI, or container environment. ## Features diff --git a/content/nginx-one/agent/configure-instances/configure-agent-group.md b/content/nginx-one-console/agent/configure-instances/configure-agent-group.md similarity index 100% rename from content/nginx-one/agent/configure-instances/configure-agent-group.md rename to content/nginx-one-console/agent/configure-instances/configure-agent-group.md diff --git a/content/nginx-one/agent/configure-instances/configure-selinux.md b/content/nginx-one-console/agent/configure-instances/configure-selinux.md similarity index 92% rename from content/nginx-one/agent/configure-instances/configure-selinux.md rename to content/nginx-one-console/agent/configure-instances/configure-selinux.md index 51297d7e3..30369a62a 100644 --- a/content/nginx-one/agent/configure-instances/configure-selinux.md +++ b/content/nginx-one-console/agent/configure-instances/configure-selinux.md @@ -17,7 +17,7 @@ Take these preparatory steps before configuring SELinux: 1. Enable SELinux on your system. 2. Install the tools `load_policy`, `semodule`, and `restorecon`. -3. [Install NGINX Agent]({{< ref "/nginx-one/agent/install-upgrade/_index.md" >}}) with SELinux module files in place. +3. [Install NGINX Agent]({{< ref "/nginx-one-console/agent/install-upgrade/_index.md" >}}) with SELinux module files in place. {{< call-out "important" >}}SELinux can use `permissive` mode, where policy violations are logged instead of enforced. Verify which mode your configuration uses.{{< /call-out >}} diff --git a/content/nginx-one/agent/configure-otel-metrics.md b/content/nginx-one-console/agent/configure-otel-metrics.md similarity index 94% rename from content/nginx-one/agent/configure-otel-metrics.md rename to content/nginx-one-console/agent/configure-otel-metrics.md index 3c76e46a4..d26086c38 100644 --- a/content/nginx-one/agent/configure-otel-metrics.md +++ b/content/nginx-one-console/agent/configure-otel-metrics.md @@ -7,7 +7,7 @@ nd-docs: DOCS-1882 ## Overview -The F5 NGINX Agent now includes an embedded [OpenTelemetry](https://opentelemetry.io) collector, streamlining observability and metric collection for NGINX instances. By default, the NGINX Agent sends key metrics to the [NGINX One Console]({{< ref "/nginx-one/nginx-configs/metrics/review-metrics" >}}), providing quick visibility into server performance through pre-configured dashboards. +The F5 NGINX Agent now includes an embedded [OpenTelemetry](https://opentelemetry.io) collector, streamlining observability and metric collection for NGINX instances. By default, the NGINX Agent sends key metrics to the [NGINX One Console]({{< ref "/nginx-one-console/nginx-configs/metrics/review-metrics" >}}), providing quick visibility into server performance through pre-configured dashboards. With this feature, you can collect: @@ -31,7 +31,7 @@ You can validate that metrics are successfully exported by using the methods bel - **NGINX One dashboard** - - When an instance has connected to NGINX One Console [See: Connect to NGINX One Console]({{< ref "/nginx-one/connect-instances/add-instance.md" >}}), you should see metrics showing on the NGINX One Console Dashboard. + - When an instance has connected to NGINX One Console [See: Connect to NGINX One Console]({{< ref "/nginx-one-console/connect-instances/add-instance.md" >}}), you should see metrics showing on the NGINX One Console Dashboard. - **Agent logs** diff --git a/content/nginx-one-console/agent/containers/_index.md b/content/nginx-one-console/agent/containers/_index.md new file mode 100644 index 000000000..4e257ce93 --- /dev/null +++ b/content/nginx-one-console/agent/containers/_index.md @@ -0,0 +1,5 @@ +--- +title: "Containers" +weight: 300 +url: /nginx-one-console/agent/containers/ +--- \ No newline at end of file diff --git a/content/nginx-one/agent/containers/run-agent-container.md b/content/nginx-one-console/agent/containers/run-agent-container.md similarity index 97% rename from content/nginx-one/agent/containers/run-agent-container.md rename to content/nginx-one-console/agent/containers/run-agent-container.md index d608c6a8e..8e52c59f7 100644 --- a/content/nginx-one/agent/containers/run-agent-container.md +++ b/content/nginx-one-console/agent/containers/run-agent-container.md @@ -44,7 +44,7 @@ Create a configuration file named `nginx-agent.conf` in your current directory and populate the file with the following structure: -{{< include "/nginx-one/conf/nginx-agent-conf.md" >}} +{{< include "/nginx-one-console/conf/nginx-agent-conf.md" >}} ## Run the container diff --git a/content/nginx-one/agent/install-upgrade/_index.md b/content/nginx-one-console/agent/install-upgrade/_index.md similarity index 50% rename from content/nginx-one/agent/install-upgrade/_index.md rename to content/nginx-one-console/agent/install-upgrade/_index.md index 0224aada9..fc9cc57c0 100644 --- a/content/nginx-one/agent/install-upgrade/_index.md +++ b/content/nginx-one-console/agent/install-upgrade/_index.md @@ -1,5 +1,5 @@ --- title: "Install and update" weight: 200 -url: /nginx-one/agent/install-upgrade/ +url: /nginx-one-console/agent/install-upgrade/ --- \ No newline at end of file diff --git a/content/nginx-one/agent/install-upgrade/install-from-github.md b/content/nginx-one-console/agent/install-upgrade/install-from-github.md similarity index 89% rename from content/nginx-one/agent/install-upgrade/install-from-github.md rename to content/nginx-one-console/agent/install-upgrade/install-from-github.md index 779594d39..0986d493e 100644 --- a/content/nginx-one/agent/install-upgrade/install-from-github.md +++ b/content/nginx-one-console/agent/install-upgrade/install-from-github.md @@ -6,11 +6,11 @@ nd-docs: DOCS-1876 --- {{< call-out "note" >}} -If you are using [NGINX One Console]({{< ref "/nginx-one/getting-started.md" >}}) +If you are using [NGINX One Console]({{< ref "/nginx-one-console/getting-started.md" >}}) to manage your NGINX instances, NGINX Agent is installed automatically when you add an NGINX instance to NGINX One Console. -For a quick guide on how to connect your instance to NGINX One Console see: [Connect to NGINX One Console]({{< ref "/nginx-one/connect-instances/add-instance.md" >}}) +For a quick guide on how to connect your instance to NGINX One Console see: [Connect to NGINX One Console]({{< ref "/nginx-one-console/connect-instances/add-instance.md" >}}) {{< /call-out >}} Follow the steps in this guide to install NGINX Agent in your NGINX instance using diff --git a/content/nginx-one/agent/install-upgrade/install-from-oss-repo.md b/content/nginx-one-console/agent/install-upgrade/install-from-oss-repo.md similarity index 91% rename from content/nginx-one/agent/install-upgrade/install-from-oss-repo.md rename to content/nginx-one-console/agent/install-upgrade/install-from-oss-repo.md index 28ee09557..b10eb547b 100644 --- a/content/nginx-one/agent/install-upgrade/install-from-oss-repo.md +++ b/content/nginx-one-console/agent/install-upgrade/install-from-oss-repo.md @@ -6,11 +6,11 @@ nd-docs: DOCS-1873 --- {{< call-out "note" >}} -If you are using [NGINX One Console]({{< ref "/nginx-one/getting-started.md" >}}) +If you are using [NGINX One Console]({{< ref "/nginx-one-console/getting-started.md" >}}) to manage your NGINX instances, NGINX Agent is installed automatically when you add an NGINX instance to NGINX One Console. -For a quick guide on how to connect your instance to NGINX One Console see: [Connect to NGINX One Console]({{< ref "/nginx-one/connect-instances/add-instance.md" >}}) +For a quick guide on how to connect your instance to NGINX One Console see: [Connect to NGINX One Console]({{< ref "/nginx-one-console/connect-instances/add-instance.md" >}}) {{< /call-out >}} ## Overview diff --git a/content/nginx-one/agent/install-upgrade/install-from-plus-repo.md b/content/nginx-one-console/agent/install-upgrade/install-from-plus-repo.md similarity index 91% rename from content/nginx-one/agent/install-upgrade/install-from-plus-repo.md rename to content/nginx-one-console/agent/install-upgrade/install-from-plus-repo.md index 939f16a4f..90932ff95 100644 --- a/content/nginx-one/agent/install-upgrade/install-from-plus-repo.md +++ b/content/nginx-one-console/agent/install-upgrade/install-from-plus-repo.md @@ -8,11 +8,11 @@ nd-docs: DOCS-1877 --- {{< call-out "note" >}} -If you are using [NGINX One Console]({{< ref "/nginx-one/getting-started.md" >}}) +If you are using [NGINX One Console]({{< ref "/nginx-one-console/getting-started.md" >}}) to manage your NGINX instances, NGINX Agent is installed automatically when you add an NGINX instance to NGINX One Console. -For a quick guide on how to connect your instance to NGINX One Console see: [Connect to NGINX One Console]({{< ref "/nginx-one/connect-instances/add-instance.md" >}}) +For a quick guide on how to connect your instance to NGINX One Console see: [Connect to NGINX One Console]({{< ref "/nginx-one-console/connect-instances/add-instance.md" >}}) {{< /call-out >}} ## Overview diff --git a/content/nginx-one/agent/install-upgrade/uninstall.md b/content/nginx-one-console/agent/install-upgrade/uninstall.md similarity index 100% rename from content/nginx-one/agent/install-upgrade/uninstall.md rename to content/nginx-one-console/agent/install-upgrade/uninstall.md diff --git a/content/nginx-one/agent/install-upgrade/update.md b/content/nginx-one-console/agent/install-upgrade/update.md similarity index 100% rename from content/nginx-one/agent/install-upgrade/update.md rename to content/nginx-one-console/agent/install-upgrade/update.md diff --git a/content/nginx-one-console/agent/overview/_index.md b/content/nginx-one-console/agent/overview/_index.md new file mode 100644 index 000000000..62e1b0814 --- /dev/null +++ b/content/nginx-one-console/agent/overview/_index.md @@ -0,0 +1,5 @@ +--- +title: "Overview" +weight: 100 +url: /nginx-one-console/agent/overview/ +--- diff --git a/content/nginx-one/agent/overview/about.md b/content/nginx-one-console/agent/overview/about.md similarity index 100% rename from content/nginx-one/agent/overview/about.md rename to content/nginx-one-console/agent/overview/about.md diff --git a/content/nginx-one/agent/overview/tech-specs.md b/content/nginx-one-console/agent/overview/tech-specs.md similarity index 100% rename from content/nginx-one/agent/overview/tech-specs.md rename to content/nginx-one-console/agent/overview/tech-specs.md diff --git a/content/nginx-one-console/agent/support/_index.md b/content/nginx-one-console/agent/support/_index.md new file mode 100644 index 000000000..cad98792c --- /dev/null +++ b/content/nginx-one-console/agent/support/_index.md @@ -0,0 +1,5 @@ +--- +title: "Support" +weight: 700 +url: /nginx-one-console/agent/support/ +--- \ No newline at end of file diff --git a/content/nginx-one/agent/support/troubleshooting.md b/content/nginx-one-console/agent/support/troubleshooting.md similarity index 100% rename from content/nginx-one/agent/support/troubleshooting.md rename to content/nginx-one-console/agent/support/troubleshooting.md diff --git a/content/nginx-one/api/_index.md b/content/nginx-one-console/api/_index.md similarity index 72% rename from content/nginx-one/api/_index.md rename to content/nginx-one-console/api/_index.md index 3a1598f3f..8a56b3b2f 100644 --- a/content/nginx-one/api/_index.md +++ b/content/nginx-one-console/api/_index.md @@ -2,5 +2,5 @@ title: Automate with the NGINX One API description: weight: 800 -url: /nginx-one/api +url: /nginx-one-console/api --- diff --git a/content/nginx-one/api/api-reference-guide.md b/content/nginx-one-console/api/api-reference-guide.md similarity index 100% rename from content/nginx-one/api/api-reference-guide.md rename to content/nginx-one-console/api/api-reference-guide.md diff --git a/content/nginx-one/api/authentication.md b/content/nginx-one-console/api/authentication.md similarity index 95% rename from content/nginx-one/api/authentication.md rename to content/nginx-one-console/api/authentication.md index 165a0401f..260fc0724 100644 --- a/content/nginx-one/api/authentication.md +++ b/content/nginx-one-console/api/authentication.md @@ -21,7 +21,7 @@ Before you begin, make sure you have either an API Token or API Certificate for You can authenticate API requests in two ways: using an API Token or an API Certificate. Below are examples of how to do this with curl, but you can also use other tools like Postman. {{< call-out "note" >}} -For definitions of terms such as _'tenant'_ and _'namespace'_ used in the following examples, refer to the [NGINX One Glossary]({{}}). +For definitions of terms such as _'tenant'_ and _'namespace'_ used in the following examples, refer to the [NGINX One Glossary]({{}}). {{< /call-out>}}
@@ -70,5 +70,5 @@ curl https://.console.ves.volterra.io/api/nginx/one/namespaces/default/d ## Further reading -- [NGINX One API Reference]({{< ref "/nginx-one/api/api-reference-guide.md" >}}) +- [NGINX One API Reference]({{< ref "/nginx-one-console/api/api-reference-guide.md" >}}) - [F5 Distributed Cloud API Documentation](https://docs.cloud.f5.com/docs/api) diff --git a/content/nginx-one/api/nginx_configuration.md b/content/nginx-one-console/api/nginx_configuration.md similarity index 95% rename from content/nginx-one/api/nginx_configuration.md rename to content/nginx-one-console/api/nginx_configuration.md index 166210be3..bd651becd 100644 --- a/content/nginx-one/api/nginx_configuration.md +++ b/content/nginx-one-console/api/nginx_configuration.md @@ -12,7 +12,7 @@ In this guide, we'll show you how to use API requests to update NGINX Configurat ## Before you begin -Before you begin, make sure you can properly authenticate your API requests with either an API Token or API Certificate, following the instructions in the [Authentication]({{}}) guide. To ensure you have registered or created your NGINX Instance, Config Sync Group, or Staged Config in the F5 NGINX One Console, follow the instructions in the [Manage your NGINX instances]({{}}) guide. +Before you begin, make sure you can properly authenticate your API requests with either an API Token or API Certificate, following the instructions in the [Authentication]({{}}) guide. To ensure you have registered or created your NGINX Instance, Config Sync Group, or Staged Config in the F5 NGINX One Console, follow the instructions in the [Manage your NGINX instances]({{}}) guide. {{< call-out "note" >}} The workflows for managing NGINX Configs for Instances, Config Sync Groups, and Staged Configs in the F5 NGINX One Console are quite similar. This guide focuses on the steps for updating NGINX Configs for Instances. If you're working with Config Sync Groups, you'll follow a similar process but will need to update the API endpoints appropriately. diff --git a/content/nginx-one/changelog.md b/content/nginx-one-console/changelog.md similarity index 81% rename from content/nginx-one/changelog.md rename to content/nginx-one-console/changelog.md index 9c1e8163b..81915a322 100644 --- a/content/nginx-one/changelog.md +++ b/content/nginx-one-console/changelog.md @@ -26,33 +26,33 @@ You can now graph any two metrics simultaneously on one chart within the Metrics ### Expanded features for configuring NGINX security policies with F5 WAF You can now configure the following for F5 WAF policies directly in the NGINX One Console: -- [Signature Sets]({{< ref "/nginx-one/waf-integration/add-signature-sets.md" >}}) -- [Signature Exceptions]({{< ref "/nginx-one/waf-integration/add-signature-sets.md#exceptions" >}}) -- [Parameters]({{< ref "/nginx-one/waf-integration/cookies-params-urls.md#add-parameters" >}}) -- [URLs]({{< ref "/nginx-one/waf-integration/cookies-params-urls.md#add-urls" >}}) -- [Cookies]({{< ref "/nginx-one/waf-integration/cookies-params-urls.md#add-cookies" >}}) +- [Signature Sets]({{< ref "/nginx-one-console/waf-integration/add-signature-sets.md" >}}) +- [Signature Exceptions]({{< ref "/nginx-one-console/waf-integration/add-signature-sets.md#exceptions" >}}) +- [Parameters]({{< ref "/nginx-one-console/waf-integration/cookies-params-urls.md#add-parameters" >}}) +- [URLs]({{< ref "/nginx-one-console/waf-integration/cookies-params-urls.md#add-urls" >}}) +- [Cookies]({{< ref "/nginx-one-console/waf-integration/cookies-params-urls.md#add-cookies" >}}) -For more details, see the [F5 WAF Integration Guide ]({{< ref "/nginx-one/waf-integration/" >}}). +For more details, see the [F5 WAF Integration Guide ]({{< ref "/nginx-one-console/waf-integration/" >}}). ## October 2, 2025 ### You can now set up config templates -- Start with how you can [Author templates]({{< ref "/nginx-one/nginx-configs/config-templates/author-templates.md" >}}) -- Automate with our **experimental** endpoints for [NGINX One Console templates]({{< ref "/nginx-one/api/api-reference-guide/#tag/Templates" >}}) +- Start with how you can [Author templates]({{< ref "/nginx-one-console/nginx-configs/config-templates/author-templates.md" >}}) +- Automate with our **experimental** endpoints for [NGINX One Console templates]({{< ref "/nginx-one-console/api/api-reference-guide/#tag/Templates" >}}) ## September 16, 2025 ### IPv6 endpoints for NGINX Agent and NGINX Plus usage reporting Your instances which run in dual-stack or IPv6-only environments can now communicate with NGINX One Console APIs through IPv6 addresses. -See the [Getting Started Guide]({{< ref "/nginx-one/getting-started.md#install-nginx-agent" >}}) for the IP address ranges you need to allow in your firewalls. +See the [Getting Started Guide]({{< ref "/nginx-one-console/getting-started.md#install-nginx-agent" >}}) for the IP address ranges you need to allow in your firewalls. ## July 15, 2025 ### Set up F5 WAF for NGINX security policies -You can now incorporate [F5 WAF for NGINX]({{< ref "/waf/" >}}) in NGINX One Console UI. For details, see [Secure with F5 WAF for NGINX]({{< ref "/nginx-one/waf-integration/" >}}). +You can now incorporate [F5 WAF for NGINX]({{< ref "/waf/" >}}) in NGINX One Console UI. For details, see [Secure with F5 WAF for NGINX]({{< ref "/nginx-one-console/waf-integration/" >}}). In NGINX One Console, you can: @@ -62,7 +62,7 @@ In NGINX One Console, you can: ### Monitor F5 NGINX Ingress Controller deployments You can now monitor your NGINX Ingress Controller deployments. For details, see how -you can [Connect to NGINX One Console]({{< ref "/nginx-one/k8s/add-nic.md" >}}). +you can [Connect to NGINX One Console]({{< ref "/nginx-one-console/k8s/add-nic.md" >}}). Unlike other NGINX instances, when you connect NGINX Ingress Controller to NGINX One Console, access is read-only. Refer to our [NGINX Ingress Controller]({{< ref "/nic/" >}}) for details on how to modify these instances. @@ -103,7 +103,7 @@ We have added API groups that align with the features and functionality in the N - Custom role assignments: You can set up custom roles for users or service accounts. - Namespace-based permissions: With [namespaces](https://docs.cloud.f5.com/docs-v2/platform/concepts/core-concepts#namespaces), you can configure API group permissions to support least privilege. -For more information, read [Custom roles and API groups]({{< ref "/nginx-one/rbac/rbac-api.md" >}}). +For more information, read [Custom roles and API groups]({{< ref "/nginx-one-console/rbac/rbac-api.md" >}}). ## March 11, 2025 @@ -113,7 +113,7 @@ It allows you to: - Save Your Progress: Staged Configurations allow you to work on configuration changes without the need for a fully functional setup. You can create these drafts from scratch, an existing Instance, another Staged Configuration, or a Config Sync Group. - No Immediate Validation Required: You don't have to immediately address syntax or configuration issues. Your Staged Configuration doesn't have to be valid until you publish it to an Instance or a Config Sync Group. -- Manage through our API: You can easily manage your Staged Configurations programmatically through our [API]({{< ref "/nginx-one/api/api-reference-guide/#tag/StagedConfigs" >}}). +- Manage through our API: You can easily manage your Staged Configurations programmatically through our [API]({{< ref "/nginx-one-console/api/api-reference-guide/#tag/StagedConfigs" >}}). ## January 20, 2025 @@ -128,8 +128,8 @@ You can: For more information, including warnings about risks, see our documentation on how you can: -- [Add a file]({{< ref "/nginx-one/nginx-configs/one-instance/add-file.md" >}}) -- [Manage certificates]({{< ref "/nginx-one/nginx-configs/certificates/manage-certificates.md" >}}) +- [Add a file]({{< ref "/nginx-one-console/nginx-configs/one-instance/add-file.md" >}}) +- [Manage certificates]({{< ref "/nginx-one-console/nginx-configs/certificates/manage-certificates.md" >}}) ### Revert a configuration @@ -153,7 +153,7 @@ From the NGINX One Console you can now: - Ensure that your certificates are current and correct. - Manage your certificates from a central location. This can help you simplify operations and remotely update, rotate, and deploy those certificates. -For more information, see the full documentation on how you can [Manage Certificates]({{< ref "/nginx-one/nginx-configs/certificates/manage-certificates.md" >}}). +For more information, see the full documentation on how you can [Manage Certificates]({{< ref "/nginx-one-console/nginx-configs/certificates/manage-certificates.md" >}}). ## August 22, 2024 @@ -161,7 +161,7 @@ For more information, see the full documentation on how you can [Manage Certific Config Sync Groups are now available in the F5 NGINX One Console. This feature allows you to manage and synchronize NGINX configurations across multiple instances as a single entity, ensuring consistency and simplifying the management of your NGINX environment. -For more information, see the full documentation on [Managing Config Sync Groups]({{< ref "/nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups.md" >}}). +For more information, see the full documentation on [Managing Config Sync Groups]({{< ref "/nginx-one-console/nginx-configs/config-sync-groups/manage-config-sync-groups.md" >}}). ## August 8, 2024 @@ -181,7 +181,7 @@ Select the link for each CVE to see the details, including the CVE's publish dat ### Edit NGINX configurations -You can now make configuration changes to your NGINX instances. For more details, see [View and edit NGINX configurations]({{< ref "/nginx-one/nginx-configs/one-instance/view-edit-nginx-configurations.md" >}}). +You can now make configuration changes to your NGINX instances. For more details, see [View and edit NGINX configurations]({{< ref "/nginx-one-console/nginx-configs/one-instance/view-edit-nginx-configurations.md" >}}). ## May 28, 2024 @@ -208,4 +208,4 @@ We've updated the **Instance Details** and **Data Plane Keys** pages to make it We're thrilled to introduce NGINX One, an exciting addition to our suite of NGINX products. Designed with efficiency and ease of use in mind, NGINX One offers an innovative approach to managing your NGINX instances. -To help you get started, take a look at the [Getting Started Guide]({{< ref "/nginx-one/getting-started.md" >}}). This guide will walk you through the initial setup and key features so you can start using NGINX One right away. +To help you get started, take a look at the [Getting Started Guide]({{< ref "/nginx-one-console/getting-started.md" >}}). This guide will walk you through the initial setup and key features so you can start using NGINX One right away. diff --git a/content/nginx-one/connect-instances/_index.md b/content/nginx-one-console/connect-instances/_index.md similarity index 59% rename from content/nginx-one/connect-instances/_index.md rename to content/nginx-one-console/connect-instances/_index.md index 686d7efc8..51d67f5db 100644 --- a/content/nginx-one/connect-instances/_index.md +++ b/content/nginx-one-console/connect-instances/_index.md @@ -2,5 +2,5 @@ description: title: Connect more instances weight: 200 -url: /nginx-one/connect-instances/ +url: /nginx-one-console/connect-instances/ --- diff --git a/content/nginx-one/connect-instances/add-instance.md b/content/nginx-one-console/connect-instances/add-instance.md similarity index 64% rename from content/nginx-one/connect-instances/add-instance.md rename to content/nginx-one-console/connect-instances/add-instance.md index 33585c398..df200b77e 100644 --- a/content/nginx-one/connect-instances/add-instance.md +++ b/content/nginx-one-console/connect-instances/add-instance.md @@ -9,23 +9,23 @@ type: ## Overview -This guide explains how to add an F5 NGINX instance in F5 NGINX One Console. You can add an instance from the NGINX One Console individually, or as part of a [Config Sync Group]({{< ref "/nginx-one/glossary.md" >}}). In either case, you need +This guide explains how to add an F5 NGINX instance in F5 NGINX One Console. You can add an instance from the NGINX One Console individually, or as part of a [Config Sync Group]({{< ref "/nginx-one-console/glossary.md" >}}). In either case, you need to set up a data plane key to connect your instances to NGINX One. ## Before you start Before you add an instance to NGINX One Console, ensure: -- You have [administrator access]({{< ref "/nginx-one/rbac/roles.md" >}}) to NGINX One Console. -- You have [configured instances of NGINX]({{< ref "/nginx-one/getting-started.md#add-your-nginx-instances-to-nginx-one" >}}) that you want to manage through NGINX One Console. -- You have or are ready to configure a [data plane key]({{< ref "/nginx-one/getting-started.md#generate-data-plane-key" >}}). -- You have or are ready to set up [managed certificates]({{< ref "/nginx-one/nginx-configs/certificates/manage-certificates.md" >}}). +- You have [administrator access]({{< ref "/nginx-one-console/rbac/roles.md" >}}) to NGINX One Console. +- You have [configured instances of NGINX]({{< ref "/nginx-one-console/getting-started.md#add-your-nginx-instances-to-nginx-one" >}}) that you want to manage through NGINX One Console. +- You have or are ready to configure a [data plane key]({{< ref "/nginx-one-console/getting-started.md#generate-data-plane-key" >}}). +- You have or are ready to set up [managed certificates]({{< ref "/nginx-one-console/nginx-configs/certificates/manage-certificates.md" >}}). -{{< call-out "note" >}}If this is the first time an instance is being added to a Config Sync Group, and you have not yet defined the configuration for that Config Sync Group, that instance provides the template for that group. For more information, see [Configuration management]({{< ref "nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups#configuration-management" >}}).{{< /call-out >}} +{{< call-out "note" >}}If this is the first time an instance is being added to a Config Sync Group, and you have not yet defined the configuration for that Config Sync Group, that instance provides the template for that group. For more information, see [Configuration management]({{< ref "/nginx-one-console/nginx-configs/config-sync-groups/manage-config-sync-groups#configuration-management" >}}).{{< /call-out >}} ## Add an instance -{{< include "/nginx-one/how-to/add-instance.md" >}} +{{< include "/nginx-one-console/how-to/add-instance.md" >}} ## Managed and Unmanaged Certificates @@ -33,7 +33,7 @@ If you add an instance with SSL/TLS certificates, those certificates can match a ### If the certificate is already managed -If you add an instance with a managed certificate, as described in [Add your NGINX instances to NGINX One]({{< ref "/nginx-one/getting-started.md#add-your-nginx-instances-to-nginx-one" >}}), these certificates are added to your list of **Managed Certificates**. +If you add an instance with a managed certificate, as described in [Add your NGINX instances to NGINX One]({{< ref "/nginx-one-console/getting-started.md#add-your-nginx-instances-to-nginx-one" >}}), these certificates are added to your list of **Managed Certificates**. NGINX One Console can manage your instances along with those certificates. @@ -53,5 +53,5 @@ Once you've completed the process, NGINX One reassigns this as a managed certifi ## Add an instance to a Config Sync Group -When you [Manage Config Sync Group membership]({{< ref "nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups#manage-config-sync-group-membership" >}}), you can add an existing or new instance to the group of your choice. +When you [Manage Config Sync Group membership]({{< ref "/nginx-one-console/nginx-configs/config-sync-groups/manage-config-sync-groups#manage-config-sync-group-membership" >}}), you can add an existing or new instance to the group of your choice. That instance inherits the setup of that Config Sync Group. diff --git a/content/nginx-one/connect-instances/connect-nginx-plus-container-images-to-nginx-one.md b/content/nginx-one-console/connect-instances/connect-nginx-plus-container-images-to-nginx-one.md similarity index 93% rename from content/nginx-one/connect-instances/connect-nginx-plus-container-images-to-nginx-one.md rename to content/nginx-one-console/connect-instances/connect-nginx-plus-container-images-to-nginx-one.md index a78490d20..31f334342 100644 --- a/content/nginx-one/connect-instances/connect-nginx-plus-container-images-to-nginx-one.md +++ b/content/nginx-one-console/connect-instances/connect-nginx-plus-container-images-to-nginx-one.md @@ -19,7 +19,7 @@ This guide explains how to set up an F5 NGINX Plus Docker container with NGINX A Before you start, make sure you have: - A valid JSON Web Token (JWT) for your NGINX subscription. -- [A data plane key from NGINX One]({{< ref "/nginx-one/connect-instances/create-manage-data-plane-keys.md" >}}). +- [A data plane key from NGINX One]({{< ref "/nginx-one-console/connect-instances/create-manage-data-plane-keys.md" >}}). - Docker installed and running on your system. #### Download your JWT license from MyF5 @@ -109,5 +109,5 @@ For more details, see: - [Deploying NGINX and NGINX Plus on Docker]({{< ref "/nginx/admin-guide/installing-nginx/installing-nginx-docker.md" >}}) - [Full List of Agent Environment Variables]({{< ref "/agent/configuration/configuration-overview.md#cli-flags-and-environment-variables" >}}) -- [NGINX One Data Plane Keys]({{< ref "/nginx-one/connect-instances/create-manage-data-plane-keys.md" >}}) +- [NGINX One Data Plane Keys]({{< ref "/nginx-one-console/connect-instances/create-manage-data-plane-keys.md" >}}) - [My F5 Knowledge Article](https://my.f5.com/manage/s/article/K000090257) diff --git a/content/nginx-one/connect-instances/connect-using-forward-proxy.md b/content/nginx-one-console/connect-instances/connect-using-forward-proxy.md similarity index 95% rename from content/nginx-one/connect-instances/connect-using-forward-proxy.md rename to content/nginx-one-console/connect-instances/connect-using-forward-proxy.md index b313ae55c..97c0fae96 100644 --- a/content/nginx-one/connect-instances/connect-using-forward-proxy.md +++ b/content/nginx-one-console/connect-instances/connect-using-forward-proxy.md @@ -13,8 +13,8 @@ proxy. This is useful in environments where direct internet access is restricted Ensure you have the following: - An explicit forward proxy server installed and configured in your network. -- [NGINX Agent is installed]({{< ref "nginx-one/agent/install-upgrade/" >}}) -- Access to the [NGINX One console]({{< ref "/nginx-one/getting-started.md#before-you-begin" >}}). +- [NGINX Agent is installed]({{< ref "/nginx-one-console/agent/install-upgrade/" >}}) +- Access to the [NGINX One console]({{< ref "/nginx-one-console/getting-started.md#before-you-begin" >}}). ## NGINX Agent configuration for proxy usage diff --git a/content/nginx-one/connect-instances/create-manage-data-plane-keys.md b/content/nginx-one-console/connect-instances/create-manage-data-plane-keys.md similarity index 97% rename from content/nginx-one/connect-instances/create-manage-data-plane-keys.md rename to content/nginx-one-console/connect-instances/create-manage-data-plane-keys.md index f12585911..d6f01e71c 100644 --- a/content/nginx-one/connect-instances/create-manage-data-plane-keys.md +++ b/content/nginx-one-console/connect-instances/create-manage-data-plane-keys.md @@ -74,4 +74,4 @@ Before you can delete a key, it must be expired or revoked. You can revoke a key ## Use the API -You can use our [API to manage your data plane keys]({{< ref "/nginx-one/api/api-reference-guide/#tag/Data-Plane/Key" >}}) in all of these ways (and more). +You can use our [API to manage your data plane keys]({{< ref "/nginx-one-console/api/api-reference-guide/#tag/Data-Plane/Key" >}}) in all of these ways (and more). diff --git a/content/nginx-one/connect-instances/set-up-nginx-proxy-for-nginx-one.md b/content/nginx-one-console/connect-instances/set-up-nginx-proxy-for-nginx-one.md similarity index 93% rename from content/nginx-one/connect-instances/set-up-nginx-proxy-for-nginx-one.md rename to content/nginx-one-console/connect-instances/set-up-nginx-proxy-for-nginx-one.md index 0f7e0b93b..3b64cb3cd 100644 --- a/content/nginx-one/connect-instances/set-up-nginx-proxy-for-nginx-one.md +++ b/content/nginx-one-console/connect-instances/set-up-nginx-proxy-for-nginx-one.md @@ -17,7 +17,7 @@ This guide explains how to set up NGINX as a proxy for other NGINX instances to ## Before you start - [Install NGINX Open Source or NGINX Plus]({{< ref "/nginx/admin-guide/installing-nginx/" >}}). -- [Get a Data Plane Key from NGINX One]({{< ref "/nginx-one/connect-instances/create-manage-data-plane-keys.md" >}}). +- [Get a Data Plane Key from NGINX One]({{< ref "/nginx-one-console/connect-instances/create-manage-data-plane-keys.md" >}}). --- @@ -118,6 +118,6 @@ To set up your other NGINX instances to use the proxy instance to connect to NGI For more information, refer to the following resources: - [Install NGINX and NGINX Plus]({{< ref "/nginx/admin-guide/installing-nginx/" >}}) -- [Create and manage data plane keys]({{< ref "/nginx-one/connect-instances/create-manage-data-plane-keys.md" >}}) +- [Create and manage data plane keys]({{< ref "/nginx-one-console/connect-instances/create-manage-data-plane-keys.md" >}}) - [NGINX Agent Installation and upgrade](https://docs.nginx.com/nginx-agent/installation-upgrade/) - [NGINX Agent Configuration](https://docs.nginx.com/nginx-agent/configuration/) diff --git a/content/nginx-one/connect-instances/settings/_index.md b/content/nginx-one-console/connect-instances/settings/_index.md similarity index 53% rename from content/nginx-one/connect-instances/settings/_index.md rename to content/nginx-one-console/connect-instances/settings/_index.md index 3bdb5095b..2984336cb 100644 --- a/content/nginx-one/connect-instances/settings/_index.md +++ b/content/nginx-one-console/connect-instances/settings/_index.md @@ -2,6 +2,6 @@ description: title: Settings weight: 500 -url: /nginx-one/connect-instances/settings +url: /nginx-one-console/connect-instances/settings draft: true --- diff --git a/content/nginx-one/getting-started.md b/content/nginx-one-console/getting-started.md similarity index 89% rename from content/nginx-one/getting-started.md rename to content/nginx-one-console/getting-started.md index ca2d4a061..af08ad736 100644 --- a/content/nginx-one/getting-started.md +++ b/content/nginx-one-console/getting-started.md @@ -8,7 +8,7 @@ nd-product: NGINX One The F5 NGINX One Console makes it easy to manage NGINX instances across locations and environments. The console lets you monitor and control your NGINX fleet from one place—you can check configurations, track performance metrics, identify security vulnerabilities, manage SSL certificates, and more. -This guide provides step-by-step instructions to activate and use F5 NGINX One Console. For a list of the latest changes, see our [changelog]({{< ref "/nginx-one/changelog.md" >}}) +This guide provides step-by-step instructions to activate and use F5 NGINX One Console. For a list of the latest changes, see our [changelog]({{< ref "/nginx-one-console/changelog.md" >}}) ## Benefits and key features @@ -43,7 +43,7 @@ If you want to register for a trial, navigate to https://account.f5.com/myf5. If ### Confirm access to the F5 Distributed Cloud -{{< include "/nginx-one/cloud-access.md" >}} +{{< include "/nginx-one-console/cloud-access.md" >}} {{< /details >}} @@ -51,7 +51,7 @@ If you want to register for a trial, navigate to https://account.f5.com/myf5. If ### Confirm access to NGINX One Console -{{< include "/nginx-one/cloud-access-nginx.md" >}} +{{< include "/nginx-one-console/cloud-access-nginx.md" >}} {{< /details >}} @@ -59,7 +59,7 @@ If you want to register for a trial, navigate to https://account.f5.com/myf5. If ### Install an instance of NGINX -{{< include "/nginx-one/install-nginx.md" >}} +{{< include "/nginx-one-console/install-nginx.md" >}} {{< /details >}} @@ -88,15 +88,15 @@ Add your NGINX instances to NGINX One. You'll need to create a data plane key an The following instructions include minimal information, sufficient to "get started." See the following links for detailed instructions: -- [Prepare - Create and manage data plane keys]({{< ref "/nginx-one/connect-instances/create-manage-data-plane-keys.md" >}}) -- [Add an NGINX instance]({{< ref "/nginx-one/connect-instances/add-instance.md" >}}) -- [Connect NGINX Plus container images]({{< ref "/nginx-one/connect-instances/connect-nginx-plus-container-images-to-nginx-one.md" >}}) +- [Prepare - Create and manage data plane keys]({{< ref "/nginx-one-console/connect-instances/create-manage-data-plane-keys.md" >}}) +- [Add an NGINX instance]({{< ref "/nginx-one-console/connect-instances/add-instance.md" >}}) +- [Connect NGINX Plus container images]({{< ref "/nginx-one-console/connect-instances/connect-nginx-plus-container-images-to-nginx-one.md" >}}) ### Generate a data plane key {#generate-data-plane-key} -{{< include "/nginx-one/how-to/generate-data-plane-key.md" >}} +{{< include "/nginx-one-console/how-to/generate-data-plane-key.md" >}} -[Revoking a data plane key]({{< ref "nginx-one/connect-instances/create-manage-data-plane-keys.md#revoke-data-plane-key" >}}) disconnects all instances that were registered with that key. +[Revoking a data plane key]({{< ref "/nginx-one-console/connect-instances/create-manage-data-plane-keys.md#revoke-data-plane-key" >}}) disconnects all instances that were registered with that key. ### Add an instance @@ -147,7 +147,7 @@ To install NGINX Agent on an NGINX instance: The `install` script writes an `nginx-agent.conf` file to the `/etc/nginx-agent/` directory, with the [data plane key](#generate-data-plane-key) that you generated. You can find this information in the `nginx-agent.conf` file: -{{< include "/nginx-one/conf/nginx-agent-conf.md" >}} +{{< include "/nginx-one-console/conf/nginx-agent-conf.md" >}} {{}} We recommend keeping `dataplane.status.poll_interval` between `30s` and `60s` in the NGINX Agent config (`/etc/nginx-agent/nginx-agent.conf`). If the interval is set above `60s`, NGINX One Console may report incorrect instance statuses.{{}} diff --git a/content/nginx-one/glossary.md b/content/nginx-one-console/glossary.md similarity index 90% rename from content/nginx-one/glossary.md rename to content/nginx-one-console/glossary.md index 540f7334c..6cde7c522 100644 --- a/content/nginx-one/glossary.md +++ b/content/nginx-one-console/glossary.md @@ -15,13 +15,13 @@ This glossary defines terms used in the F5 NGINX One Console and F5 Distributed | Term | Definition | |-------------|-------------| -| **Config Sync Group** | A group of NGINX systems (or instances) with identical configurations. They may also share the same certificates. However, the instances in a Config Sync Group could belong to different systems and even different clusters. For more information, see this explanation of [Important considerations]({{< ref "/nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups.md#important-considerations" >}}) | +| **Config Sync Group** | A group of NGINX systems (or instances) with identical configurations. They may also share the same certificates. However, the instances in a Config Sync Group could belong to different systems and even different clusters. For more information, see this explanation of [Important considerations]({{< ref "/nginx-one-console/nginx-configs/config-sync-groups/manage-config-sync-groups.md#important-considerations" >}}) | | **Control Plane** | The control plane is the part of a network architecture that manages and controls the flow or data or traffic (the Data Plane). It is responsible for system-level tasks such as routing and traffic management. | | **Data Plane** | The data plane is the part of a network architecture that carries user traffic. It handles tasks like forwarding data packets between devices and managing network communication. In the context of NGINX, the data plane is responsible for tasks such as load balancing, caching, and serving web content. | | **Instance** | An instance is an individual system with NGINX installed. You can group the instances of your choice in a Config Sync Group. When you add an instance to NGINX One, you need to use a data plane key. | | **Namespace** | In F5 Distributed Cloud, a namespace groups a tenant’s configuration objects, similar to administrative domains. Every object in a namespace must have a unique name, and each namespace must be unique to its tenant. This setup ensures isolation, preventing cross-referencing of objects between namespaces. You'll see the namespace in the NGINX One Console URL as `/namespaces//`. To switch an instance between namespaces, you have to deregister an instance from an old namespace, and register it on the new namespace. | | **NGINX Agent** | A lightweight software component installed on NGINX instances to enable communication with the NGINX One console. | -| **Staged Configurations** | Also known as **Staged Configs**. Allows you to save "work in progress." You can create it from scratch, an Instance, another Staged Config, or a Config Sync Group. It does _not_ have to be a working configuration until you publish it to an instance or a Config Sync Group. You can even manage your **Staged Configurations** through our [API]({{< ref "/nginx-one/api/api-reference-guide/#tag/StagedConfigs" >}}). | +| **Staged Configurations** | Also known as **Staged Configs**. Allows you to save "work in progress." You can create it from scratch, an Instance, another Staged Config, or a Config Sync Group. It does _not_ have to be a working configuration until you publish it to an instance or a Config Sync Group. You can even manage your **Staged Configurations** through our [API]({{< ref "/nginx-one-console/api/api-reference-guide/#tag/StagedConfigs" >}}). | | **Tenant** | A tenant in F5 Distributed Cloud is an entity that owns a specific set of configuration and infrastructure. It is fundamental for isolation, meaning a tenant cannot access objects or infrastructure of other tenants. Tenants can be either individual or enterprise, with the latter allowing multiple users with role-based access control (RBAC). | {{< /table >}} @@ -32,9 +32,9 @@ This glossary defines terms used in the F5 NGINX One Console and F5 Distributed ## NGINX Alerts -To set up NGINX Alerts through the F5 Distributed Cloud, follow the procedure in [Set up security alerts]({{< ref "/nginx-one/secure-your-fleet/set-up-security-alerts/" >}}). +To set up NGINX Alerts through the F5 Distributed Cloud, follow the procedure in [Set up security alerts]({{< ref "/nginx-one-console/secure-your-fleet/set-up-security-alerts/" >}}). -{{< include "/nginx-one/alert-labels.md" >}} +{{< include "/nginx-one-console/alert-labels.md" >}} ## Legal notice: Licensing agreements for NGINX products diff --git a/content/nginx-one/k8s/_index.md b/content/nginx-one-console/k8s/_index.md similarity index 77% rename from content/nginx-one/k8s/_index.md rename to content/nginx-one-console/k8s/_index.md index 794456588..e24e959f7 100644 --- a/content/nginx-one/k8s/_index.md +++ b/content/nginx-one-console/k8s/_index.md @@ -2,7 +2,7 @@ title: Connect Kubernetes deployments description: weight: 700 -url: /nginx-one/k8s +url: /nginx-one-console/k8s nd-product: NGINX One --- diff --git a/content/nginx-one/k8s/add-ngf-helm.md b/content/nginx-one-console/k8s/add-ngf-helm.md similarity index 93% rename from content/nginx-one/k8s/add-ngf-helm.md rename to content/nginx-one-console/k8s/add-ngf-helm.md index 680987ff1..aca0e5801 100644 --- a/content/nginx-one/k8s/add-ngf-helm.md +++ b/content/nginx-one-console/k8s/add-ngf-helm.md @@ -16,7 +16,7 @@ Once connected, you'll see a **read-only** configuration of NGINX Gateway Fabric ## Before you begin -Log in to NGINX One Console. If you need more information, review our [Get started guide]({{< ref "/nginx-one/getting-started.md#before-you-begin" >}}). +Log in to NGINX One Console. If you need more information, review our [Get started guide]({{< ref "/nginx-one-console/getting-started.md#before-you-begin" >}}). You also need: @@ -25,11 +25,11 @@ You also need: ### Create a data plane key -{{< include "/nginx-one/how-to/generate-data-plane-key.md" >}} +{{< include "/nginx-one-console/how-to/generate-data-plane-key.md" >}} ### Create a Kubernetes secret with the data plane key -{{< include "/nginx-one/how-to/k8s-secret-dp-key.md" >}} +{{< include "/nginx-one-console/how-to/k8s-secret-dp-key.md" >}} ## Install Gateway API resources @@ -139,8 +139,8 @@ kubectl wait --timeout=5m -n nginx-gateway deployment/ngf-nginx-gateway-fabric - ## Verify a connection to NGINX One Console -{{< include "/nginx-one/how-to/verify-connection.md" >}} +{{< include "/nginx-one-console/how-to/verify-connection.md" >}} ## Troubleshooting -{{< include "/nginx-one/how-to/ngf-troubleshooting.md" >}} +{{< include "/nginx-one-console/how-to/ngf-troubleshooting.md" >}} diff --git a/content/nginx-one/k8s/add-ngf-manifests.md b/content/nginx-one-console/k8s/add-ngf-manifests.md similarity index 80% rename from content/nginx-one/k8s/add-ngf-manifests.md rename to content/nginx-one-console/k8s/add-ngf-manifests.md index b7d675331..6823d389d 100644 --- a/content/nginx-one/k8s/add-ngf-manifests.md +++ b/content/nginx-one-console/k8s/add-ngf-manifests.md @@ -16,17 +16,17 @@ Once connected, you'll see a **read-only** configuration of NGINX Gateway Fabric ## Before you begin -Log in to NGINX One Console. If you need more information, review our [Get started guide]({{< ref "/nginx-one/getting-started.md#before-you-begin" >}}). +Log in to NGINX One Console. If you need more information, review our [Get started guide]({{< ref "/nginx-one-console/getting-started.md#before-you-begin" >}}). {{< include "/ngf/installation/install-manifests-prereqs.md" >}} ### Create a data plane key -{{< include "/nginx-one/how-to/generate-data-plane-key.md" >}} +{{< include "/nginx-one-console/how-to/generate-data-plane-key.md" >}} ### Create a Kubernetes secret with the data plane key -{{< include "/nginx-one/how-to/k8s-secret-dp-key.md" >}} +{{< include "/nginx-one-console/how-to/k8s-secret-dp-key.md" >}} ## Install Gateway API resources @@ -45,11 +45,11 @@ Specify the data plane key Secret name in the `--nginx-one-dataplane-key-secret` ## Verify a connection to NGINX One Console -{{< include "/nginx-one/how-to/verify-connection.md" >}} +{{< include "/nginx-one-console/how-to/verify-connection.md" >}} ## Troubleshooting -{{< include "/nginx-one/how-to/ngf-troubleshooting.md" >}} +{{< include "/nginx-one-console/how-to/ngf-troubleshooting.md" >}} ## References diff --git a/content/nginx-one/k8s/add-nic.md b/content/nginx-one-console/k8s/add-nic.md similarity index 95% rename from content/nginx-one/k8s/add-nic.md rename to content/nginx-one-console/k8s/add-nic.md index 006e9a5ff..605011202 100644 --- a/content/nginx-one/k8s/add-nic.md +++ b/content/nginx-one-console/k8s/add-nic.md @@ -16,7 +16,7 @@ Once connected, you'll see a **read-only** configuration of NGINX Ingress Contro ## Before you begin -If you do not already have a [data plane key]({{< ref "/nginx-one/connect-instances/create-manage-data-plane-keys.md" >}}), you can create one. Pay attention to the expiration date of that key. Any instance that's connected to a data plane key that's expired or revoked will stop working. +If you do not already have a [data plane key]({{< ref "/nginx-one-console/connect-instances/create-manage-data-plane-keys.md" >}}), you can create one. Pay attention to the expiration date of that key. Any instance that's connected to a data plane key that's expired or revoked will stop working. You can create a data plane key through the NGINX One Console. Once loggged in, select **Manage > Control Planes > Add Control Plane**, and follow the steps shown. @@ -63,7 +63,7 @@ Upgrade or install NGINX Ingress Controller with the following command to config --set nginxAgent.endpointHost=agent.connect.nginx.com ``` -The `dataplaneKeySecretName` is used to authenticate the agent with NGINX One Console. See the [NGINX One Console Docs]({{< ref "/nginx-one/connect-instances/create-manage-data-plane-keys.md" >}}) +The `dataplaneKeySecretName` is used to authenticate the agent with NGINX One Console. See the [NGINX One Console Docs]({{< ref "/nginx-one-console/connect-instances/create-manage-data-plane-keys.md" >}}) for instructions on how to generate your dataplane key from the NGINX One Console. Follow the [Installation with Helm]({{< ref "/nic/install/helm.md" >}}) instructions to deploy NGINX Ingress Controller. diff --git a/content/nginx-one/k8s/overview.md b/content/nginx-one-console/k8s/overview.md similarity index 100% rename from content/nginx-one/k8s/overview.md rename to content/nginx-one-console/k8s/overview.md diff --git a/content/nginx-one/nginx-configs/_index.md b/content/nginx-one-console/nginx-configs/_index.md similarity index 64% rename from content/nginx-one/nginx-configs/_index.md rename to content/nginx-one-console/nginx-configs/_index.md index d4a987147..9c9fab97e 100644 --- a/content/nginx-one/nginx-configs/_index.md +++ b/content/nginx-one-console/nginx-configs/_index.md @@ -2,5 +2,5 @@ description: title: Manage your NGINX instances weight: 300 -url: /nginx-one/nginx-configs +url: /nginx-one-console/nginx-configs --- diff --git a/content/nginx-one/nginx-configs/certificates/_index.md b/content/nginx-one-console/nginx-configs/certificates/_index.md similarity index 56% rename from content/nginx-one/nginx-configs/certificates/_index.md rename to content/nginx-one-console/nginx-configs/certificates/_index.md index b97d42034..2919587e7 100644 --- a/content/nginx-one/nginx-configs/certificates/_index.md +++ b/content/nginx-one-console/nginx-configs/certificates/_index.md @@ -2,5 +2,5 @@ description: title: Monitor your certificates weight: 500 -url: /nginx-one/nginx-configs/certificates +url: /nginx-one-console/nginx-configs/certificates --- diff --git a/content/nginx-one/nginx-configs/certificates/manage-certificates.md b/content/nginx-one-console/nginx-configs/certificates/manage-certificates.md similarity index 91% rename from content/nginx-one/nginx-configs/certificates/manage-certificates.md rename to content/nginx-one-console/nginx-configs/certificates/manage-certificates.md index efadce2a0..ad700f4ca 100644 --- a/content/nginx-one/nginx-configs/certificates/manage-certificates.md +++ b/content/nginx-one-console/nginx-configs/certificates/manage-certificates.md @@ -22,7 +22,7 @@ You may have separate sets of SSL/TLS certificates, as described in the followin | NGINX Licensing | /etc/ssl/nginx/server.crt
/etc/ssl/nginx/server.key | Supports access to repositories. Based on licenses downloaded from https://my.f5.com/ | {{}} -Allowed directories depend on the [NGINX Agent]({{< ref "/nginx-one/getting-started/#install-nginx-agent" >}}). Look for the `/etc/nginx-agent/nginx-agent.conf` file. +Allowed directories depend on the [NGINX Agent]({{< ref "/nginx-one-console/getting-started/#install-nginx-agent" >}}). Look for the `/etc/nginx-agent/nginx-agent.conf` file. Find the `config_dirs` parameter in that file, as described in the NGINX Agent [Basic configuration](https://docs.nginx.com/nginx-agent/configuration/configuration-overview/#cli-flags--environment-variables). You may need to add a directory like `/etc/ssl` to that parameter. @@ -34,8 +34,8 @@ From the NGINX One Console you can: You can manage the certificates for: -- [Unique instances]({{< ref "/nginx-one/nginx-configs/one-instance/add-file.md#new-ssl-certificate-or-ca-bundle" >}}) -- For all instances that are members of a [Config Sync Group]({{< ref "/nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups/#configuration-management" >}}) +- [Unique instances]({{< ref "/nginx-one-console/nginx-configs/one-instance/add-file.md#new-ssl-certificate-or-ca-bundle" >}}) +- For all instances that are members of a [Config Sync Group]({{< ref "/nginx-one-console/nginx-configs/config-sync-groups/manage-config-sync-groups/#configuration-management" >}}) {{< call-out "tip" >}} @@ -49,7 +49,7 @@ If you are managing the certificate from NGINX One Console, we recommend that yo Before you add and manage certificates with the NGINX One Console make sure: - You have access to the NGINX One Console -- You have access through the F5 Distributed Cloud role, as described in the [Authentication]({{< ref "/nginx-one/api/authentication.md" >}}) guide, to manage SSL/TLS certificates +- You have access through the F5 Distributed Cloud role, as described in the [Authentication]({{< ref "/nginx-one-console/api/authentication.md" >}}) guide, to manage SSL/TLS certificates - You have the `f5xc-nginx-one-user` role for your account - Your SSL/TLS certificates and keys match @@ -174,7 +174,7 @@ If that certificate is managed and is part of a Config Sync Group, that change a ## Managed and unmanaged certificates -If you register an instance to NGINX One Console, as described in [Add your NGINX instances to NGINX One]({{< ref "/nginx-one/getting-started.md#add-your-nginx-instances-to-nginx-one" >}}), and the associated SSL/TLS certificates: +If you register an instance to NGINX One Console, as described in [Add your NGINX instances to NGINX One]({{< ref "/nginx-one-console/getting-started.md#add-your-nginx-instances-to-nginx-one" >}}), and the associated SSL/TLS certificates: - Are used in their NGINX configuration - Do _not_ match an existing managed SSL certificate/CA bundle @@ -193,6 +193,6 @@ To convert these cerificates to managed, start with the Certificates menu, and s ## See also -- [Create and manage data plane keys]({{< ref "/nginx-one/connect-instances/create-manage-data-plane-keys.md" >}}) -- [Add an instance]({{< ref "/nginx-one/connect-instances/add-instance.md" >}}) -- [Add a file in a configuration]({{< ref "/nginx-one/nginx-configs/one-instance/add-file.md" >}}) +- [Create and manage data plane keys]({{< ref "/nginx-one-console/connect-instances/create-manage-data-plane-keys.md" >}}) +- [Add an instance]({{< ref "/nginx-one-console/connect-instances/add-instance.md" >}}) +- [Add a file in a configuration]({{< ref "/nginx-one-console/nginx-configs/one-instance/add-file.md" >}}) diff --git a/content/nginx-one/nginx-configs/clean-up-unavailable-instances.md b/content/nginx-one-console/nginx-configs/clean-up-unavailable-instances.md similarity index 95% rename from content/nginx-one/nginx-configs/clean-up-unavailable-instances.md rename to content/nginx-one-console/nginx-configs/clean-up-unavailable-instances.md index e198b4566..ec69436e7 100644 --- a/content/nginx-one/nginx-configs/clean-up-unavailable-instances.md +++ b/content/nginx-one-console/nginx-configs/clean-up-unavailable-instances.md @@ -16,7 +16,7 @@ This guide explains how to set up automatic cleanup for NGINX instances in NGINX Before you set up automatic cleanup for NGINX instances, ensure: -- You have [administrator access]({{< ref "/nginx-one/rbac/roles.md" >}}) to NGINX One Console. +- You have [administrator access]({{< ref "/nginx-one-console/rbac/roles.md" >}}) to NGINX One Console. - You understand that this action will delete instances permanently after they are unavailable for the specified duration. ## Configure instance cleanup diff --git a/content/nginx-one/nginx-configs/config-sync-groups/_index.md b/content/nginx-one-console/nginx-configs/config-sync-groups/_index.md similarity index 58% rename from content/nginx-one/nginx-configs/config-sync-groups/_index.md rename to content/nginx-one-console/nginx-configs/config-sync-groups/_index.md index 96d90f3e3..1da776820 100644 --- a/content/nginx-one/nginx-configs/config-sync-groups/_index.md +++ b/content/nginx-one-console/nginx-configs/config-sync-groups/_index.md @@ -2,5 +2,5 @@ description: title: Change multiple instances with one push weight: 400 -url: /nginx-one/nginx-configs/config-sync-groups +url: /nginx-one-console/nginx-configs/config-sync-groups --- diff --git a/content/nginx-one/nginx-configs/config-sync-groups/add-file-csg.md b/content/nginx-one-console/nginx-configs/config-sync-groups/add-file-csg.md similarity index 65% rename from content/nginx-one/nginx-configs/config-sync-groups/add-file-csg.md rename to content/nginx-one-console/nginx-configs/config-sync-groups/add-file-csg.md index aec837d21..36b76be2c 100644 --- a/content/nginx-one/nginx-configs/config-sync-groups/add-file-csg.md +++ b/content/nginx-one-console/nginx-configs/config-sync-groups/add-file-csg.md @@ -9,7 +9,7 @@ type: ## Overview -{{< include "nginx-one/add-file/overview.md" >}} +{{< include "/nginx-one-console/add-file/overview.md" >}} ## Before you start @@ -20,7 +20,7 @@ Before you add files in your configuration, ensure: ## Important considerations -This page applies when you want to add a file to a Config Sync Group. Any changes you make here apply to all [Instances]({{< ref "/nginx-one/glossary.md" >}}) of that Config Sync Group. +This page applies when you want to add a file to a Config Sync Group. Any changes you make here apply to all [Instances]({{< ref "/nginx-one-console/glossary.md" >}}) of that Config Sync Group. ## Add a file @@ -31,7 +31,7 @@ You can use the NGINX One Console to add a file to a specific Config Sync Group. {{< call-out "tip" >}} - {{< include "nginx-one/add-file/edit-config-tip.md" >}} + {{< include "/nginx-one-console/add-file/edit-config-tip.md" >}} {{< /call-out >}} @@ -46,7 +46,7 @@ Enter the name of the desired configuration file, such as `abc.conf` and select ### New SSL Certificate or CA Bundle -{{< include "nginx-one/add-file/new-ssl-bundle.md" >}} +{{< include "/nginx-one-console/add-file/new-ssl-bundle.md" >}} {{< call-out "tip" >}} @@ -57,12 +57,12 @@ Enter the name of the desired configuration file, such as `abc.conf` and select ### Existing SSL Certificate or CA Bundle -{{< include "nginx-one/add-file/existing-ssl-bundle.md" >}} +{{< include "/nginx-one-console/add-file/existing-ssl-bundle.md" >}} -With this option, you can incorporate [Managed certificates]({{< ref "/nginx-one/nginx-configs/certificates/manage-certificates.md#managed-and-unmanaged-certificates" >}}). +With this option, you can incorporate [Managed certificates]({{< ref "/nginx-one-console/nginx-configs/certificates/manage-certificates.md#managed-and-unmanaged-certificates" >}}). ## See also -- [Create and manage data plane keys]({{< ref "/nginx-one/connect-instances/create-manage-data-plane-keys.md" >}}) -- [Add an NGINX instance]({{< ref "/nginx-one/connect-instances/add-instance.md" >}}) -- [Manage certificates]({{< ref "/nginx-one/nginx-configs/certificates/manage-certificates.md" >}}) +- [Create and manage data plane keys]({{< ref "/nginx-one-console/connect-instances/create-manage-data-plane-keys.md" >}}) +- [Add an NGINX instance]({{< ref "/nginx-one-console/connect-instances/add-instance.md" >}}) +- [Manage certificates]({{< ref "/nginx-one-console/nginx-configs/certificates/manage-certificates.md" >}}) diff --git a/content/nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups.md b/content/nginx-one-console/nginx-configs/config-sync-groups/manage-config-sync-groups.md similarity index 98% rename from content/nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups.md rename to content/nginx-one-console/nginx-configs/config-sync-groups/manage-config-sync-groups.md index d7e919b35..d02b6d7d3 100644 --- a/content/nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups.md +++ b/content/nginx-one-console/nginx-configs/config-sync-groups/manage-config-sync-groups.md @@ -202,7 +202,7 @@ When adding a new NGINX instance that is not yet registered with NGINX One, you Data plane keys are required for registering NGINX instances with the NGINX One Console. These keys serve as secure tokens, ensuring that only authorized instances can connect and communicate with NGINX One. -For more details on creating and managing data plane keys, see [Create and manage data plane keys]({{}}). +For more details on creating and managing data plane keys, see [Create and manage data plane keys]({{}}). {{}} @@ -331,6 +331,6 @@ Monitor the **Config Sync Status** column. It can help you ensure that your conf ## See also -- [Create and manage data plane keys]({{< ref "/nginx-one/connect-instances/create-manage-data-plane-keys.md" >}}) -- [Add an NGINX instance]({{< ref "/nginx-one/connect-instances/add-instance.md" >}}) +- [Create and manage data plane keys]({{< ref "/nginx-one-console/connect-instances/create-manage-data-plane-keys.md" >}}) +- [Add an NGINX instance]({{< ref "/nginx-one-console/connect-instances/add-instance.md" >}}) - [Updating the NGINX configuration with an NGINX One Console Config Sync Group push fails (My F5 Knowledge article)](https://my.f5.com/manage/s/article/K000154659) diff --git a/content/nginx-one/nginx-configs/config-templates/_index.md b/content/nginx-one-console/nginx-configs/config-templates/_index.md similarity index 53% rename from content/nginx-one/nginx-configs/config-templates/_index.md rename to content/nginx-one-console/nginx-configs/config-templates/_index.md index 8394c9f16..fa2095628 100644 --- a/content/nginx-one/nginx-configs/config-templates/_index.md +++ b/content/nginx-one-console/nginx-configs/config-templates/_index.md @@ -2,5 +2,5 @@ description: title: Manage config templates weight: 400 -url: /nginx-one/nginx-configs/config-templates +url: /nginx-one-console/nginx-configs/config-templates --- diff --git a/content/nginx-one/nginx-configs/config-templates/add-multiple-services.md b/content/nginx-one-console/nginx-configs/config-templates/add-multiple-services.md similarity index 100% rename from content/nginx-one/nginx-configs/config-templates/add-multiple-services.md rename to content/nginx-one-console/nginx-configs/config-templates/add-multiple-services.md diff --git a/content/nginx-one/nginx-configs/config-templates/author-templates.md b/content/nginx-one-console/nginx-configs/config-templates/author-templates.md similarity index 100% rename from content/nginx-one/nginx-configs/config-templates/author-templates.md rename to content/nginx-one-console/nginx-configs/config-templates/author-templates.md diff --git a/content/nginx-one/nginx-configs/config-templates/import-templates.md b/content/nginx-one-console/nginx-configs/config-templates/import-templates.md similarity index 97% rename from content/nginx-one/nginx-configs/config-templates/import-templates.md rename to content/nginx-one-console/nginx-configs/config-templates/import-templates.md index 5e89f92fc..d437e9dee 100644 --- a/content/nginx-one/nginx-configs/config-templates/import-templates.md +++ b/content/nginx-one-console/nginx-configs/config-templates/import-templates.md @@ -23,8 +23,8 @@ In this guide, you will learn how to: Make sure you have the following: -- Access to the NGINX One Console in your organization. See [Before you begin]({{< ref "/nginx-one/getting-started.md#before-you-begin" >}}) in the Get started guide. -- API credentials for the Templates API. See [Authenticate with the API]({{< ref "/nginx-one/api/authentication.md" >}}). +- Access to the NGINX One Console in your organization. See [Before you begin]({{< ref "/nginx-one-console/getting-started.md#before-you-begin" >}}) in the Get started guide. +- API credentials for the Templates API. See [Authenticate with the API]({{< ref "/nginx-one-console/api/authentication.md" >}}). - The `tar` command installed. - The **absolute path** to your NGINX configuration file (for example, `/etc/nginx/nginx.conf`). This path is required when submitting templates for preview. @@ -296,7 +296,7 @@ ls -la *.tar.gz ### Ready to import -After creating the archives, import them using the [Import a template API]({{< ref "/nginx-one/api/api-reference-guide/#operation/importTemplate" >}}) operation. +After creating the archives, import them using the [Import a template API]({{< ref "/nginx-one-console/api/api-reference-guide/#operation/importTemplate" >}}) operation. #### Required API parameters diff --git a/content/nginx-one/nginx-configs/config-templates/save-as-staged-config.md b/content/nginx-one-console/nginx-configs/config-templates/save-as-staged-config.md similarity index 90% rename from content/nginx-one/nginx-configs/config-templates/save-as-staged-config.md rename to content/nginx-one-console/nginx-configs/config-templates/save-as-staged-config.md index f44a5deef..6ade7536d 100644 --- a/content/nginx-one/nginx-configs/config-templates/save-as-staged-config.md +++ b/content/nginx-one-console/nginx-configs/config-templates/save-as-staged-config.md @@ -10,7 +10,7 @@ nd-product: NGINX One Console # Overview -This guide explains how to save a [Submission]({{< ref "submit-templates.md#make-the-request" >}}) response as a new [Staged Config]({{< ref "/nginx-one/nginx-configs/staged-configs" >}}). +This guide explains how to save a [Submission]({{< ref "submit-templates.md#make-the-request" >}}) response as a new [Staged Config]({{< ref "/nginx-one-console/nginx-configs/staged-configs" >}}). # How to save @@ -33,7 +33,7 @@ Use the `config` object from the API response in step 1 to create a staged confi ### Make the request -Use the [Create a staged config]({{< ref "/nginx-one/api/api-reference-guide/#operation/createStagedConfig" >}}) API operation. +Use the [Create a staged config]({{< ref "/nginx-one-console/api/api-reference-guide/#operation/createStagedConfig" >}}) API operation. ### Request body @@ -104,6 +104,6 @@ Here's an example of what you need to include with the API request: ## See also - [Submit Templates Guide]({{< ref "submit-templates.md" >}}) -- [Staged Configs]({{< ref "/nginx-one/nginx-configs/staged-configs" >}}) +- [Staged Configs]({{< ref "/nginx-one-console/nginx-configs/staged-configs" >}}) diff --git a/content/nginx-one/nginx-configs/config-templates/submit-templates.md b/content/nginx-one-console/nginx-configs/config-templates/submit-templates.md similarity index 95% rename from content/nginx-one/nginx-configs/config-templates/submit-templates.md rename to content/nginx-one-console/nginx-configs/config-templates/submit-templates.md index 17647b409..91d655805 100644 --- a/content/nginx-one/nginx-configs/config-templates/submit-templates.md +++ b/content/nginx-one-console/nginx-configs/config-templates/submit-templates.md @@ -39,7 +39,7 @@ Before creating a submission, find base and augment templates that match your in ### List available templates -Use the [List Templates]({{< ref "/nginx-one/api/api-reference-guide/#operation/listTemplates" >}}) API operation to find templates organized by use case. +Use the [List Templates]({{< ref "/nginx-one-console/api/api-reference-guide/#operation/listTemplates" >}}) API operation to find templates organized by use case. **Example response:** @@ -106,7 +106,7 @@ The API response contains all information needed for creating a submission to re ### Get template details (optional) -Use the [Retrieve a Template]({{< ref "/nginx-one/api/api-reference-guide/#operation/getTemplate" >}}) API operation only when you need to examine template content or detailed variable requirements. +Use the [Retrieve a Template]({{< ref "/nginx-one-console/api/api-reference-guide/#operation/getTemplate" >}}) API operation only when you need to examine template content or detailed variable requirements. **When to use template details:** @@ -161,7 +161,7 @@ Use the [Retrieve a Template]({{< ref "/nginx-one/api/api-reference-guide/#opera ## API endpoint -Use the [Submit templates for previewing NGINX configuration]({{< ref "/nginx-one/api/api-reference-guide/#operation/submitTemplates" >}}) API operation to render and preview NGINX configurations from templates. +Use the [Submit templates for previewing NGINX configuration]({{< ref "/nginx-one-console/api/api-reference-guide/#operation/submitTemplates" >}}) API operation to render and preview NGINX configurations from templates. ## Request structure @@ -233,7 +233,7 @@ For more information, see [Understanding Rendering Order](#understanding-renderi ## Make the request -Use the [Submit Templates]({{< ref "/nginx-one/api/api-reference-guide/#operation/submitTemplates" >}}) API operation with your composed request and the required `preview_only=true` parameter. +Use the [Submit Templates]({{< ref "/nginx-one-console/api/api-reference-guide/#operation/submitTemplates" >}}) API operation with your composed request and the required `preview_only=true` parameter. ### Request body diff --git a/content/nginx-one/nginx-configs/metrics/_index.md b/content/nginx-one-console/nginx-configs/metrics/_index.md similarity index 62% rename from content/nginx-one/nginx-configs/metrics/_index.md rename to content/nginx-one-console/nginx-configs/metrics/_index.md index 9602b6a8b..943b3ec21 100644 --- a/content/nginx-one/nginx-configs/metrics/_index.md +++ b/content/nginx-one-console/nginx-configs/metrics/_index.md @@ -2,5 +2,5 @@ description: title: Set up metrics weight: 500 -url: /nginx-one/metrics/ +url: /nginx-one-console/metrics/ --- diff --git a/content/nginx-one/nginx-configs/metrics/enable-metrics.md b/content/nginx-one-console/nginx-configs/metrics/enable-metrics.md similarity index 85% rename from content/nginx-one/nginx-configs/metrics/enable-metrics.md rename to content/nginx-one-console/nginx-configs/metrics/enable-metrics.md index 93fde0642..def4a8e8c 100644 --- a/content/nginx-one/nginx-configs/metrics/enable-metrics.md +++ b/content/nginx-one-console/nginx-configs/metrics/enable-metrics.md @@ -24,7 +24,7 @@ To display metrics, complete the following steps: ## Enable NGINX Plus API and dashboard with Config Sync Groups -To enable the NGINX Plus API and dashboard with [Config Sync Groups]({{< ref "nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups.md" >}}), add a file named `/etc/nginx/conf.d/dashboard.conf` to your shared group config. Any instance you add to that group automatically uses those settings. +To enable the NGINX Plus API and dashboard with [Config Sync Groups]({{< ref "/nginx-one-console/nginx-configs/config-sync-groups/manage-config-sync-groups.md" >}}), add a file named `/etc/nginx/conf.d/dashboard.conf` to your shared group config. Any instance you add to that group automatically uses those settings. {{< include "use-cases/monitoring/enable-nginx-plus-api-with-config-sync-group.md" >}} diff --git a/content/nginx-one/nginx-configs/metrics/review-metrics.md b/content/nginx-one-console/nginx-configs/metrics/review-metrics.md similarity index 100% rename from content/nginx-one/nginx-configs/metrics/review-metrics.md rename to content/nginx-one-console/nginx-configs/metrics/review-metrics.md diff --git a/content/nginx-one/nginx-configs/one-instance/_index.md b/content/nginx-one-console/nginx-configs/one-instance/_index.md similarity index 58% rename from content/nginx-one/nginx-configs/one-instance/_index.md rename to content/nginx-one-console/nginx-configs/one-instance/_index.md index 6577c95a0..89307d2cb 100644 --- a/content/nginx-one/nginx-configs/one-instance/_index.md +++ b/content/nginx-one-console/nginx-configs/one-instance/_index.md @@ -2,5 +2,5 @@ description: title: Manage a single NGINX instance weight: 300 -url: /nginx-one/nginx-configs/one-instance +url: /nginx-one-console/nginx-configs/one-instance --- diff --git a/content/nginx-one/nginx-configs/one-instance/add-file.md b/content/nginx-one-console/nginx-configs/one-instance/add-file.md similarity index 60% rename from content/nginx-one/nginx-configs/one-instance/add-file.md rename to content/nginx-one-console/nginx-configs/one-instance/add-file.md index 5c4cecb72..cd329d6b9 100644 --- a/content/nginx-one/nginx-configs/one-instance/add-file.md +++ b/content/nginx-one-console/nginx-configs/one-instance/add-file.md @@ -9,19 +9,19 @@ type: ## Overview -{{< include "nginx-one/add-file/overview.md" >}} +{{< include "/nginx-one-console/add-file/overview.md" >}} ## Before you start Before you add files in your configuration, ensure: -- You have [access to the NGINX One Console]({{< ref "/nginx-one/rbac/roles.md" >}}). -- NGINX instances are [properly registered]({{< ref "/nginx-one/getting-started.md#add-your-nginx-instances-to-nginx-one" >}}) with NGINX One Console. +- You have [access to the NGINX One Console]({{< ref "/nginx-one-console/rbac/roles.md" >}}). +- NGINX instances are [properly registered]({{< ref "/nginx-one-console/getting-started.md#add-your-nginx-instances-to-nginx-one" >}}) with NGINX One Console. ## Important considerations If your instance is a member of a Config Sync Group, changes that you make may be synchronized to other instances in that group. -For more information, see how you can [Manage Config Sync Groups]({{< ref "/nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups.md" >}}). +For more information, see how you can [Manage Config Sync Groups]({{< ref "/nginx-one-console/nginx-configs/config-sync-groups/manage-config-sync-groups.md" >}}). ## Add a file @@ -32,7 +32,7 @@ You can use the NGINX One Console to add a file to a specific instance. To do so {{< call-out "tip" >}} - {{< include "nginx-one/add-file/edit-config-tip.md" >}} + {{< include "/nginx-one-console/add-file/edit-config-tip.md" >}} {{< /call-out >}} @@ -47,7 +47,7 @@ Enter the name of the desired configuration file, such as `abc.conf` and select ### New SSL Certificate or CA Bundle -{{< include "nginx-one/add-file/new-ssl-bundle.md" >}} +{{< include "/nginx-one-console/add-file/new-ssl-bundle.md" >}} {{< call-out "tip" >}} @@ -58,10 +58,10 @@ Enter the name of the desired configuration file, such as `abc.conf` and select ### Existing SSL Certificate or CA Bundle -{{< include "nginx-one/add-file/existing-ssl-bundle.md" >}} +{{< include "/nginx-one-console/add-file/existing-ssl-bundle.md" >}} ## See also -- [Create and manage data plane keys]({{< ref "/nginx-one/connect-instances/create-manage-data-plane-keys.md" >}}) -- [Add an NGINX instance]({{< ref "/nginx-one/connect-instances/add-instance.md" >}}) -- [Manage certificates]({{< ref "/nginx-one/nginx-configs/certificates/manage-certificates.md" >}}) +- [Create and manage data plane keys]({{< ref "/nginx-one-console/connect-instances/create-manage-data-plane-keys.md" >}}) +- [Add an NGINX instance]({{< ref "/nginx-one-console/connect-instances/add-instance.md" >}}) +- [Manage certificates]({{< ref "/nginx-one-console/nginx-configs/certificates/manage-certificates.md" >}}) diff --git a/content/nginx-one/nginx-configs/one-instance/view-edit-nginx-configurations.md b/content/nginx-one-console/nginx-configs/one-instance/view-edit-nginx-configurations.md similarity index 87% rename from content/nginx-one/nginx-configs/one-instance/view-edit-nginx-configurations.md rename to content/nginx-one-console/nginx-configs/one-instance/view-edit-nginx-configurations.md index 5ad4ab137..9393b6e89 100644 --- a/content/nginx-one/nginx-configs/one-instance/view-edit-nginx-configurations.md +++ b/content/nginx-one-console/nginx-configs/one-instance/view-edit-nginx-configurations.md @@ -24,8 +24,8 @@ To view and edit an NGINX configuration, follow these steps: 6. When you are satisfied with the changes, select **Next**. 7. Compare and verify your changes before selecting **Save and Publish** to publish the edited configuration. -Alternatively, you can select **Save Changes As**. In the window that appears, you can set up this instance as a [**Staged Configuration**]({{< ref "/nginx-one/nginx-configs/staged-configs/_index.md" >}}). +Alternatively, you can select **Save Changes As**. In the window that appears, you can set up this instance as a [**Staged Configuration**]({{< ref "/nginx-one-console/nginx-configs/staged-configs/_index.md" >}}). ## See also -- [Manage Config Sync Groups]({{< ref "/nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups.md" >}}) +- [Manage Config Sync Groups]({{< ref "/nginx-one-console/nginx-configs/config-sync-groups/manage-config-sync-groups.md" >}}) diff --git a/content/nginx-one/nginx-configs/staged-configs/_index.md b/content/nginx-one-console/nginx-configs/staged-configs/_index.md similarity index 55% rename from content/nginx-one/nginx-configs/staged-configs/_index.md rename to content/nginx-one-console/nginx-configs/staged-configs/_index.md index ddb5f35fb..a7dd2b017 100644 --- a/content/nginx-one/nginx-configs/staged-configs/_index.md +++ b/content/nginx-one-console/nginx-configs/staged-configs/_index.md @@ -2,5 +2,5 @@ description: title: Draft new configurations weight: 400 -url: /nginx-one/nginx-configs/staged-configs +url: /nginx-one-console/nginx-configs/staged-configs --- diff --git a/content/nginx-one/nginx-configs/staged-configs/add-staged-config.md b/content/nginx-one-console/nginx-configs/staged-configs/add-staged-config.md similarity index 97% rename from content/nginx-one/nginx-configs/staged-configs/add-staged-config.md rename to content/nginx-one-console/nginx-configs/staged-configs/add-staged-config.md index 196d6c34a..f14cbff41 100644 --- a/content/nginx-one/nginx-configs/staged-configs/add-staged-config.md +++ b/content/nginx-one-console/nginx-configs/staged-configs/add-staged-config.md @@ -16,7 +16,7 @@ product: NGINX-One This guide explains how to add a Staged Configuration to your NGINX One Console. -{{< include "nginx-one/staged-config-overview.md" >}} +{{< include "/nginx-one-console/staged-config-overview.md" >}} ## Before you start diff --git a/content/nginx-one/nginx-configs/staged-configs/api-staged-config.md b/content/nginx-one-console/nginx-configs/staged-configs/api-staged-config.md similarity index 74% rename from content/nginx-one/nginx-configs/staged-configs/api-staged-config.md rename to content/nginx-one-console/nginx-configs/staged-configs/api-staged-config.md index 18c276ae3..9fd9b3cde 100644 --- a/content/nginx-one/nginx-configs/staged-configs/api-staged-config.md +++ b/content/nginx-one-console/nginx-configs/staged-configs/api-staged-config.md @@ -13,8 +13,8 @@ product: NGINX-One You can use F5 NGINX One Console API to manage your Staged Configurations. With our API, you can: -- [Create an NGINX Staged Configuration]({{< ref "/nginx-one/api/api-reference-guide/#operation/createStagedConfig" >}}) +- [Create an NGINX Staged Configuration]({{< ref "/nginx-one-console/api/api-reference-guide/#operation/createStagedConfig" >}}) - The details allow you to add existing configuration files. -- [Get a list of existing Staged Configurations]({{< ref "/nginx-one/api/api-reference-guide/#operation/listStagedConfigs" >}}) +- [Get a list of existing Staged Configurations]({{< ref "/nginx-one-console/api/api-reference-guide/#operation/listStagedConfigs" >}}) - Be sure to record the `object_id` of your target Staged Configuration for your analysis report. -- [Get an analysis report for an existing Staged Configuration]({{< ref "/nginx-one/api/api-reference-guide/#operation/getStagedConfigReport" >}}) +- [Get an analysis report for an existing Staged Configuration]({{< ref "/nginx-one-console/api/api-reference-guide/#operation/getStagedConfigReport" >}}) diff --git a/content/nginx-one/nginx-configs/staged-configs/edit-staged-config.md b/content/nginx-one-console/nginx-configs/staged-configs/edit-staged-config.md similarity index 96% rename from content/nginx-one/nginx-configs/staged-configs/edit-staged-config.md rename to content/nginx-one-console/nginx-configs/staged-configs/edit-staged-config.md index 8f101a0fd..2fe97c104 100644 --- a/content/nginx-one/nginx-configs/staged-configs/edit-staged-config.md +++ b/content/nginx-one-console/nginx-configs/staged-configs/edit-staged-config.md @@ -15,7 +15,7 @@ product: NGINX One This guide explains how to edit an existing Staged Configuration in your NGINX One Console. -{{< include "nginx-one/staged-config-overview.md" >}} +{{< include "/nginx-one-console/staged-config-overview.md" >}} ## Before you start diff --git a/content/nginx-one/nginx-configs/staged-configs/import-export-staged-config.md b/content/nginx-one-console/nginx-configs/staged-configs/import-export-staged-config.md similarity index 93% rename from content/nginx-one/nginx-configs/staged-configs/import-export-staged-config.md rename to content/nginx-one-console/nginx-configs/staged-configs/import-export-staged-config.md index de713dc21..f8c4ca9e9 100644 --- a/content/nginx-one/nginx-configs/staged-configs/import-export-staged-config.md +++ b/content/nginx-one-console/nginx-configs/staged-configs/import-export-staged-config.md @@ -18,7 +18,7 @@ Many administrators do their work on local systems, virtual machines, Docker con supports import and export of such configurations. This guide explains how to import or export a Staged Configuration to your NGINX One Console. -{{< include "nginx-one/staged-config-overview.md" >}} +{{< include "/nginx-one-console/staged-config-overview.md" >}} ## Before you start @@ -26,7 +26,7 @@ Before you import or export a Staged Configuration to NGINX One Console, ensure: - You have an NGINX One Console account with staged configuration permissions. -You can also import, export, and manage multiple Staged Configurations through [the API]({{< ref "/nginx-one/nginx-configs/staged-configs/api-staged-config.md" >}}). +You can also import, export, and manage multiple Staged Configurations through [the API]({{< ref "/nginx-one-console/nginx-configs/staged-configs/api-staged-config.md" >}}). ## Considerations @@ -86,4 +86,4 @@ You can also delete multiple Staged Configurations through the UI: 1. Select the Staged Configuration you want to delete. 1. You can then select the **Delete selected** button. -You can do more from the API. Specifically, with the `object_id` of each configuration, you can create, modify, or delete multiple staged configurations with the [Bulk Staged Configurations endpoint]({{< ref "/nginx-one/api/api-reference-guide/#operation/bulkStagedConfigs" >}}). +You can do more from the API. Specifically, with the `object_id` of each configuration, you can create, modify, or delete multiple staged configurations with the [Bulk Staged Configurations endpoint]({{< ref "/nginx-one-console/api/api-reference-guide/#operation/bulkStagedConfigs" >}}). diff --git a/content/nginx-one/rbac/_index.md b/content/nginx-one-console/rbac/_index.md similarity index 69% rename from content/nginx-one/rbac/_index.md rename to content/nginx-one-console/rbac/_index.md index 447611e56..c4677a45c 100644 --- a/content/nginx-one/rbac/_index.md +++ b/content/nginx-one-console/rbac/_index.md @@ -2,5 +2,5 @@ title: Organize users with RBAC description: weight: 600 -url: /nginx-one/rbac +url: /nginx-one-console/rbac --- diff --git a/content/nginx-one/rbac/overview.md b/content/nginx-one-console/rbac/overview.md similarity index 100% rename from content/nginx-one/rbac/overview.md rename to content/nginx-one-console/rbac/overview.md diff --git a/content/nginx-one/rbac/rbac-api.md b/content/nginx-one-console/rbac/rbac-api.md similarity index 95% rename from content/nginx-one/rbac/rbac-api.md rename to content/nginx-one-console/rbac/rbac-api.md index 97187bec2..c0c1f9e47 100644 --- a/content/nginx-one/rbac/rbac-api.md +++ b/content/nginx-one-console/rbac/rbac-api.md @@ -7,7 +7,7 @@ product: NGINX One nd-docs: DOCS-000 --- -Beyond the [Default roles]({{< ref "/nginx-one/rbac/roles.md" >}}) for NGINX One Console access, you can create [custom roles](https://docs.cloud.f5.com/docs-v2/administration/how-tos/user-mgmt/roles#custom-roles) with more precisely defined access permissions. +Beyond the [Default roles]({{< ref "/nginx-one-console/rbac/roles.md" >}}) for NGINX One Console access, you can create [custom roles](https://docs.cloud.f5.com/docs-v2/administration/how-tos/user-mgmt/roles#custom-roles) with more precisely defined access permissions. You can assign custom roles to users or service accounts. You can associate these roles with specific [namespaces](https://docs.cloud.f5.com/docs-v2/multi-cloud-app-connect/how-to/app-security/service-policy), to help facilitate the principle of least privilege across your tenant. diff --git a/content/nginx-one/rbac/roles.md b/content/nginx-one-console/rbac/roles.md similarity index 100% rename from content/nginx-one/rbac/roles.md rename to content/nginx-one-console/rbac/roles.md diff --git a/content/nginx-one/secure-your-fleet/_index.md b/content/nginx-one-console/secure-your-fleet/_index.md similarity index 58% rename from content/nginx-one/secure-your-fleet/_index.md rename to content/nginx-one-console/secure-your-fleet/_index.md index d9fea82ff..0edc577d1 100644 --- a/content/nginx-one/secure-your-fleet/_index.md +++ b/content/nginx-one-console/secure-your-fleet/_index.md @@ -2,5 +2,5 @@ title: Secure your fleet description: weight: 450 -url: /nginx-one/secure-your-fleet +url: /nginx-one-console/secure-your-fleet --- diff --git a/content/nginx-one/secure-your-fleet/set-up-security-alerts.md b/content/nginx-one-console/secure-your-fleet/set-up-security-alerts.md similarity index 90% rename from content/nginx-one/secure-your-fleet/set-up-security-alerts.md rename to content/nginx-one-console/secure-your-fleet/set-up-security-alerts.md index 2f02b4180..14f8e49d4 100644 --- a/content/nginx-one/secure-your-fleet/set-up-security-alerts.md +++ b/content/nginx-one-console/secure-your-fleet/set-up-security-alerts.md @@ -27,7 +27,7 @@ If you already have accessed F5 Distributed Cloud and have NGINX instances avail ### Confirm access to the F5 Distributed Cloud -{{< include "/nginx-one/cloud-access.md" >}} +{{< include "/nginx-one-console/cloud-access.md" >}} ### Confirm access to NGINX One Console in the F5 Distributed Cloud @@ -43,20 +43,20 @@ Alternatively, we also have instructions for [Deploying NGINX and NGINX Plus wit ## Connect at least one NGINX instance to the NGINX One Console -If you already have connected instances to the NGINX One Console, you can start to [Configure an active alert policy]({{< ref "/nginx-one/secure-your-fleet/set-up-security-alerts.md#configure-an-active-alert-policy" >}}). +If you already have connected instances to the NGINX One Console, you can start to [Configure an active alert policy]({{< ref "/nginx-one-console/secure-your-fleet/set-up-security-alerts.md#configure-an-active-alert-policy" >}}). Otherwise, you need to add an instance, generate a data plane key, and install NGINX Agent. We assume this is the first time you are connecting an instance. ### Add an instance -{{< include "/nginx-one/how-to/add-instance.md" >}} +{{< include "/nginx-one-console/how-to/add-instance.md" >}} ### Generate a data plane key -{{< include "/nginx-one/how-to/generate-data-plane-key.md" >}} +{{< include "/nginx-one-console/how-to/generate-data-plane-key.md" >}} ### Install NGINX Agent -{{< include "/nginx-one/how-to/install-nginx-agent.md" >}} +{{< include "/nginx-one-console/how-to/install-nginx-agent.md" >}} You can also install NGINX Agent from our repositories and configure it manually. Alternatively you can use our official NGINX Docker images, pre-configured with NGINX Agent. @@ -90,7 +90,7 @@ To configure security-related alerts, follow these steps: ## Configure Alert Policy -Next, configure the policy that identifies when you'll get an alert. You'll need to reference available alerts in our [NGINX One Console Glossary]({{< ref "/nginx-one/glossary.md#nginx-alerts/" >}}). Relevant security alerts include: +Next, configure the policy that identifies when you'll get an alert. You'll need to reference available alerts in our [NGINX One Console Glossary]({{< ref "/nginx-one-console/glossary.md#nginx-alerts/" >}}). Relevant security alerts include: - SecurityRecommendationNGINX - HighCVENGINX @@ -105,7 +105,7 @@ Next, configure the policy that identifies when you'll get an alert. You'll need 1. Under **Policy Rules** select **Configure**. 1. In the **Policy Rules** screen that appears, select **Add Item**. 1. In the **Route** window that appears, review the **Select Alerts** drop-down. -1. Under **Select Alerts** select a filter. Now select **Matching Custom Criteria > Alertname > Configure**. In the screen that appears, use **Exact Match** and copy/paste an alert name from the [NGINX One Console Glossary]({{< ref "/nginx-one/glossary.md#nginx-alerts" >}}). +1. Under **Select Alerts** select a filter. Now select **Matching Custom Criteria > Alertname > Configure**. In the screen that appears, use **Exact Match** and copy/paste an alert name from the [NGINX One Console Glossary]({{< ref "/nginx-one-console/glossary.md#nginx-alerts" >}}). 1. Select **Apply** to exit the **Alertname** window. 1. Select **Apply** to exit the **Route** window. 1. Select **Apply** to exit the **Policy Rules** window. @@ -115,7 +115,7 @@ Next, configure the policy that identifies when you'll get an alert. You'll need ## Create more alert policies Repeat the process described in [Configure Alert Policy](#configure-alert-policy) section. Repeat again if and as needed for all of the alerts in the -[NGINX One Console Glossary]({{< ref "/nginx-one/glossary.md#nginx-alerts/" >}}). +[NGINX One Console Glossary]({{< ref "/nginx-one-console/glossary.md#nginx-alerts/" >}}). ## Activate the alert policy @@ -164,5 +164,5 @@ You will now receive an email any time the F5 Distributed Cloud sees one or more ## Next steps -Now that you have NGINX instances connected to the NGINX One Console, consider reviewing our [use cases]({{< ref "/nginx-one/" >}}) to see how you can easily manage your NGINX instances, draft new configurations, and more. +Now that you have NGINX instances connected to the NGINX One Console, consider reviewing our [use cases]({{< ref "/nginx-one-console/" >}}) to see how you can easily manage your NGINX instances, draft new configurations, and more. Additionally, you can review how to add additional Alert Receivers such as [SMS](https://docs.cloud.f5.com/docs-v2/shared-configuration/how-tos/alerting/alerts-email-sms), [Slack](https://docs.cloud.f5.com/docs-v2/shared-configuration/how-tos/alerting/alerts-slack), [PagerDuty](https://docs.cloud.f5.com/docs-v2/shared-configuration/how-tos/alerting/alerts-pagerduty), or with a [webhook](https://docs.cloud.f5.com/docs-v2/shared-configuration/how-tos/alerting/alerts-webhook). diff --git a/content/nginx-one/waf-integration/_index.md b/content/nginx-one-console/waf-integration/_index.md similarity index 63% rename from content/nginx-one/waf-integration/_index.md rename to content/nginx-one-console/waf-integration/_index.md index 168f7cee6..8f700d1a0 100644 --- a/content/nginx-one/waf-integration/_index.md +++ b/content/nginx-one-console/waf-integration/_index.md @@ -2,5 +2,5 @@ title: Secure with F5 WAF for NGINX description: weight: 400 -url: /nginx-one/waf-integration +url: /nginx-one-console/waf-integration --- diff --git a/content/nginx-one/waf-integration/add-signature-sets.md b/content/nginx-one-console/waf-integration/add-signature-sets.md similarity index 94% rename from content/nginx-one/waf-integration/add-signature-sets.md rename to content/nginx-one-console/waf-integration/add-signature-sets.md index f892d5613..5b750edf2 100644 --- a/content/nginx-one/waf-integration/add-signature-sets.md +++ b/content/nginx-one-console/waf-integration/add-signature-sets.md @@ -123,10 +123,10 @@ After configuring signature sets and exceptions: 1. Select **Add Policy**. The policy JSON will be updated with your changes. 1. Your policy will appear in the list under the name you provided. -1. You can then [deploy]({{< ref "/nginx-one/waf-integration/deploy-policy.md/" >}}) the policy to either: +1. You can then [deploy]({{< ref "/nginx-one-console/waf-integration/deploy-policy.md/" >}}) the policy to either: - An instance - A Config Sync Group -From NGINX One Console, you can [review and modify]({{< ref "/nginx-one/waf-integration/review-policy.md/" >}}) your saved policies at any time by selecting **App Protect > Policies**. +From NGINX One Console, you can [review and modify]({{< ref "/nginx-one-console/waf-integration/review-policy.md/" >}}) your saved policies at any time by selecting **App Protect > Policies**. For a complete list of available signature sets and detailed information about attack signatures, see the [Attack Signatures]({{< ref "/waf/policies/attack-signatures.md" >}}) documentation. diff --git a/content/nginx-one/waf-integration/configure-policy.md b/content/nginx-one-console/waf-integration/configure-policy.md similarity index 91% rename from content/nginx-one/waf-integration/configure-policy.md rename to content/nginx-one-console/waf-integration/configure-policy.md index 4aba70e0d..72aca8dbf 100644 --- a/content/nginx-one/waf-integration/configure-policy.md +++ b/content/nginx-one-console/waf-integration/configure-policy.md @@ -27,7 +27,7 @@ From NGINX One Console, select App Protect > Policies. In the screen that appear - Transparent - Blocking -For details, see the [Glossary]({{< ref "/nginx-one/glossary.md#nginx-app-protect-waf-terminology" >}}), specifically the entry: **Enforcement mode**. You'll see this in the associated configuration file, +For details, see the [Glossary]({{< ref "/nginx-one-console/glossary.md#nginx-app-protect-waf-terminology" >}}), specifically the entry: **Enforcement mode**. You'll see this in the associated configuration file, with the `enforcementMode` property. You can also set a character encoding. The default encoding is `Unicode (utf-8)`. To set a different character encoding, select **Show Advanced Fields** and select the **Application Language** of your choice. diff --git a/content/nginx-one/waf-integration/cookies-params-urls.md b/content/nginx-one-console/waf-integration/cookies-params-urls.md similarity index 90% rename from content/nginx-one/waf-integration/cookies-params-urls.md rename to content/nginx-one-console/waf-integration/cookies-params-urls.md index efabf4d9f..e0f6fd291 100644 --- a/content/nginx-one/waf-integration/cookies-params-urls.md +++ b/content/nginx-one-console/waf-integration/cookies-params-urls.md @@ -13,7 +13,7 @@ Cookie protections can be configured and managed directly within the policy edit ## Cookie properties and types Each cookie configuration includes: -- `Cookie Type`: `Explicit` or `Wildcard`. For details on explicit and wildcard matching, see the [Matching Types: Explicit vs Wildcard]({{< ref "/nginx-one/waf-integration/waf-policy-matching-types.md" >}}) section. +- `Cookie Type`: `Explicit` or `Wildcard`. For details on explicit and wildcard matching, see the [Matching Types: Explicit vs Wildcard]({{< ref "/nginx-one-console/waf-integration/waf-policy-matching-types.md" >}}) section. - `Cookie Name`: The name of the cookie to be monitored or protected - `Enforcement Type`: - **Allow**: Specifies that this cookie may be changed by the client. The cookie is not protected from modification @@ -37,7 +37,7 @@ For each violation type, you can: - Set the enforcement action - Toggle `Alarm`, `Alarm and Block`, or `Disabled` settings -For more details about enforcement modes, see the [Glossary]({{< ref "/nginx-one/glossary.md#nginx-app-protect-waf-terminology" >}}), specifically the entry: **Enforcement mode**. +For more details about enforcement modes, see the [Glossary]({{< ref "/nginx-one-console/glossary.md#nginx-app-protect-waf-terminology" >}}), specifically the entry: **Enforcement mode**. See the [Supported Violations]({{< ref "/waf/policies/violations.md#supported-violations" >}}) for additional details. @@ -55,7 +55,7 @@ See the [Supported Violations]({{< ref "/waf/policies/violations.md#supported-vi 1. Optional: Configure Attack Signatures - If enabled, you can overwrite attack signatures for this specific cookie - - For details on signature configuration, refer to the documentation on [Add Signature Sets]({{< ref "/nginx-one/waf-integration/add-signature-sets.md/" >}}) + - For details on signature configuration, refer to the documentation on [Add Signature Sets]({{< ref "/nginx-one-console/waf-integration/add-signature-sets.md/" >}}) 1. Select **Add Cookie** to save your configuration @@ -67,7 +67,7 @@ Parameter protections can be configured and managed directly within the policy e Each parameter configuration includes: -- `Parameter Type`: `Explicit` or `Wildcard`. For details on explicit and wildcard matching, see the [Matching Types: Explicit vs Wildcard]({{< ref "/nginx-one/waf-integration/waf-policy-matching-types.md" >}}) section. +- `Parameter Type`: `Explicit` or `Wildcard`. For details on explicit and wildcard matching, see the [Matching Types: Explicit vs Wildcard]({{< ref "/nginx-one-console/waf-integration/waf-policy-matching-types.md" >}}) section. - `Parameter Name`: The name of the parameter - `Location`: Where the parameter is expected (URL query string, POST data, etc.) - `Value Type`: The expected type of the parameter value (e.g., alpha-numeric, integer, email) @@ -100,7 +100,7 @@ For each violation type, you can: - Set the enforcement action - Toggle `Alarm`, `Alarm and Block`, or `Disabled` settings -For more details about enforcement modes, see the [Glossary]({{< ref "/nginx-one/glossary.md#nginx-app-protect-waf-terminology" >}}), specifically the entry: **Enforcement mode**. +For more details about enforcement modes, see the [Glossary]({{< ref "/nginx-one-console/glossary.md#nginx-app-protect-waf-terminology" >}}), specifically the entry: **Enforcement mode**. See the [Supported Violations]({{< ref "/waf/policies/violations.md#supported-violations" >}}) for additional details. @@ -128,7 +128,7 @@ See the [Supported Violations]({{< ref "/waf/policies/violations.md#supported-vi 1. Optional: Configure Attack Signatures - If enabled, you can overwrite attack signatures for this specific parameter - - For details on signature configuration, refer to the documentation on [Add Signature Sets]({{< ref "/nginx-one/waf-integration/add-signature-sets.md/" >}}) + - For details on signature configuration, refer to the documentation on [Add Signature Sets]({{< ref "/nginx-one-console/waf-integration/add-signature-sets.md/" >}}) 1. Select **Add Parameter** to save your configuration @@ -139,7 +139,7 @@ URL protections can be configured and managed directly within the policy editor ## URL properties and types Each URL configuration includes: -- `URL Type`: `Explicit` or `Wildcard`. For details on explicit and wildcard matching, see the [Matching Types: Explicit vs Wildcard]({{< ref "/nginx-one/waf-integration/waf-policy-matching-types.md" >}}) section. +- `URL Type`: `Explicit` or `Wildcard`. For details on explicit and wildcard matching, see the [Matching Types: Explicit vs Wildcard]({{< ref "/nginx-one-console/waf-integration/waf-policy-matching-types.md" >}}) section. - `Method`: Specifies the HTTP method(s) for the URL (`GET`, `POST`, `PUT`, etc.) - `Protocol`: The protocol for the URL (`HTTP`/`HTTPS`) - `Enforcement Type`: @@ -168,7 +168,7 @@ For each violation type, you can: - Set the enforcement action - Toggle `Alarm`, `Alarm and Block`, or `Disabled` settings -For more details about enforcement modes, see the [Glossary]({{< ref "/nginx-one/glossary.md#nginx-app-protect-waf-terminology" >}}), specifically the entry: **Enforcement mode**. +For more details about enforcement modes, see the [Glossary]({{< ref "/nginx-one-console/glossary.md#nginx-app-protect-waf-terminology" >}}), specifically the entry: **Enforcement mode**. See the [Supported Violations]({{< ref "/waf/policies/violations.md#supported-violations" >}}) for additional details. @@ -195,6 +195,6 @@ See the [Supported Violations]({{< ref "/waf/policies/violations.md#supported-vi 1. **Optional**: Configure Attack Signatures - If enabled, you can overwrite attack signatures for this specific URL - - For details on signature configuration, refer to the documentation on [Add Signature Sets]({{< ref "/nginx-one/waf-integration/add-signature-sets.md/" >}}) + - For details on signature configuration, refer to the documentation on [Add Signature Sets]({{< ref "/nginx-one-console/waf-integration/add-signature-sets.md/" >}}) 1. Select **Add URL** to save your configuration diff --git a/content/nginx-one/waf-integration/deploy-policy.md b/content/nginx-one-console/waf-integration/deploy-policy.md similarity index 100% rename from content/nginx-one/waf-integration/deploy-policy.md rename to content/nginx-one-console/waf-integration/deploy-policy.md diff --git a/content/nginx-one/waf-integration/overview.md b/content/nginx-one-console/waf-integration/overview.md similarity index 85% rename from content/nginx-one/waf-integration/overview.md rename to content/nginx-one-console/waf-integration/overview.md index ae695aeea..3f6b237e4 100644 --- a/content/nginx-one/waf-integration/overview.md +++ b/content/nginx-one-console/waf-integration/overview.md @@ -21,11 +21,11 @@ Once you've connected to the NGINX One Console, select **App Protect > Policies* Through the NGINX One Console UI, you can: -- [Add and configure a policy]({{< ref "/nginx-one/waf-integration/configure-policy.md/" >}}) -- [Review existing policies]({{< ref "/nginx-one/waf-integration/review-policy.md/" >}}) -- [Deploy policies]({{< ref "/nginx-one/waf-integration/deploy-policy.md/" >}}) on instances and Config Sync Groups +- [Add and configure a policy]({{< ref "/nginx-one-console/waf-integration/configure-policy.md/" >}}) +- [Review existing policies]({{< ref "/nginx-one-console/waf-integration/review-policy.md/" >}}) +- [Deploy policies]({{< ref "/nginx-one-console/waf-integration/deploy-policy.md/" >}}) on instances and Config Sync Groups -You can also set up policies through the [NGINX One Console API]({{< ref "/nginx-one/waf-integration/security-policy-api.md/" >}}). +You can also set up policies through the [NGINX One Console API]({{< ref "/nginx-one-console/waf-integration/security-policy-api.md/" >}}). ## Set up F5 WAF for NGINX diff --git a/content/nginx-one/waf-integration/review-policy.md b/content/nginx-one-console/waf-integration/review-policy.md similarity index 100% rename from content/nginx-one/waf-integration/review-policy.md rename to content/nginx-one-console/waf-integration/review-policy.md diff --git a/content/nginx-one/waf-integration/security-policy-api.md b/content/nginx-one-console/waf-integration/security-policy-api.md similarity index 56% rename from content/nginx-one/waf-integration/security-policy-api.md rename to content/nginx-one-console/waf-integration/security-policy-api.md index fbcf860af..217e23711 100644 --- a/content/nginx-one/waf-integration/security-policy-api.md +++ b/content/nginx-one-console/waf-integration/security-policy-api.md @@ -8,13 +8,13 @@ product: NGINX One You can use F5 NGINX One Console API to manage security policies. With our API, you can: -- [List existing policies]({{< ref "/nginx-one/api/api-reference-guide/#operation/listNapPolicies" >}}) +- [List existing policies]({{< ref "/nginx-one-console/api/api-reference-guide/#operation/listNapPolicies" >}}) - You can set parameters to sort policies by type. -- [Create a new policy]({{< ref "/nginx-one/api/api-reference-guide/#operation/createNapPolicy" >}}) +- [Create a new policy]({{< ref "/nginx-one-console/api/api-reference-guide/#operation/createNapPolicy" >}}) - You need to translate the desired policy.json file to base64 format. -- [Get policy details]({{< ref "/nginx-one/api/api-reference-guide/#operation/getNapPolicy" >}}) +- [Get policy details]({{< ref "/nginx-one-console/api/api-reference-guide/#operation/getNapPolicy" >}}) - Returns details of the policy you identified with the policy `object_id`. -- [List F5 WAF for NGINX Deployments]({{< ref "/nginx-one/api/api-reference-guide/#operation/listNapPolicyDeployments" >}}) +- [List F5 WAF for NGINX Deployments]({{< ref "/nginx-one-console/api/api-reference-guide/#operation/listNapPolicyDeployments" >}}) - The output includes: - Target of the deployment - Time of deployment diff --git a/content/nginx-one/waf-integration/waf-policy-matching-types.md b/content/nginx-one-console/waf-integration/waf-policy-matching-types.md similarity index 100% rename from content/nginx-one/waf-integration/waf-policy-matching-types.md rename to content/nginx-one-console/waf-integration/waf-policy-matching-types.md diff --git a/content/nginx-one/workshops/_index.md b/content/nginx-one-console/workshops/_index.md similarity index 71% rename from content/nginx-one/workshops/_index.md rename to content/nginx-one-console/workshops/_index.md index 944f2b055..c64d85426 100644 --- a/content/nginx-one/workshops/_index.md +++ b/content/nginx-one-console/workshops/_index.md @@ -2,7 +2,7 @@ title: Workshops description: weight: 710 -url: /nginx-one/workshops +url: /nginx-one-console/workshops nd-landing-page: true nd-content-type: landing-page nd-product: NGINX One @@ -17,23 +17,23 @@ We recommend starting with Lab 1 and Lab 2. Lab 2 sets up the workshop environme {{}} - {{}} + {{}} Register instances. Learn about managing your NGINX fleet. {{}} - {{}} + {{}} Use Docker to spin up the full workshop locally. {{}} - {{}} + {{}} Take a guided tour of NGINX One Console. Explore dashboards, alerts, and insights while trying out key features. {{}} - {{}} + {{}} Create and manage Config Sync Groups to apply consistent changes across all your NGINX instances. {{}} - {{}} + {{}} Plan and upgrade NGINX Plus with NGINX One Console workflows, keeping downtime to a minimum. {{}} diff --git a/content/nginx-one/workshops/lab1/getting-started-with-nginx-one-console.md b/content/nginx-one-console/workshops/lab1/getting-started-with-nginx-one-console.md similarity index 86% rename from content/nginx-one/workshops/lab1/getting-started-with-nginx-one-console.md rename to content/nginx-one-console/workshops/lab1/getting-started-with-nginx-one-console.md index b7a1cf2a7..cfc847cd2 100644 --- a/content/nginx-one/workshops/lab1/getting-started-with-nginx-one-console.md +++ b/content/nginx-one-console/workshops/lab1/getting-started-with-nginx-one-console.md @@ -41,7 +41,7 @@ You need: - NGINX One service enabled - Basic Linux and NGINX knowledge -{{< include "/nginx-one/cloud-access.md" >}} +{{< include "/nginx-one-console/cloud-access.md" >}} --- @@ -62,13 +62,13 @@ When you register a new instance, NGINX One Console gives you a `curl` command t A data plane key is required to connect an instance to NGINX One Console. Once connected, you can monitor and manage the instance from the dashboard. -For more about NGINX Agent, see the [NGINX Agent overview]({{< ref "/nginx-one/agent/overview/about.md" >}}). +For more about NGINX Agent, see the [NGINX Agent overview]({{< ref "/nginx-one-console/agent/overview/about.md" >}}). --- ## Open NGINX One Console -{{< include "/nginx-one/cloud-access-nginx.md" >}} +{{< include "/nginx-one-console/cloud-access-nginx.md" >}} Until you connect NGINX instances, the NGINX One Console dashboard is empty. After you add instances, the dashboard shows metrics such as availability, version, and usage trends. @@ -112,11 +112,11 @@ You can delete a data plane key only after you revoke it. You’re ready to connect your first NGINX instance to NGINX One Console. -Go to [Lab 2: Run workshop components with Docker]({{< ref "nginx-one/workshops/lab2/run-workshop-components-with-docker.md" >}}). +Go to [Lab 2: Run workshop components with Docker]({{< ref "/nginx-one-console/workshops/lab2/run-workshop-components-with-docker.md" >}}). --- ## References -- [Create and manage data plane keys]({{< ref "nginx-one/connect-instances/create-manage-data-plane-keys.md" >}}) -- [NGINX Agent overview]({{< ref "/nginx-one/agent/overview/about.md" >}}) \ No newline at end of file +- [Create and manage data plane keys]({{< ref "/nginx-one-console/connect-instances/create-manage-data-plane-keys.md" >}}) +- [NGINX Agent overview]({{< ref "/nginx-one-console/agent/overview/about.md" >}}) \ No newline at end of file diff --git a/content/nginx-one/workshops/lab2/run-workshop-components-with-docker.md b/content/nginx-one-console/workshops/lab2/run-workshop-components-with-docker.md similarity index 88% rename from content/nginx-one/workshops/lab2/run-workshop-components-with-docker.md rename to content/nginx-one-console/workshops/lab2/run-workshop-components-with-docker.md index 418ac2087..14ac57238 100644 --- a/content/nginx-one/workshops/lab2/run-workshop-components-with-docker.md +++ b/content/nginx-one-console/workshops/lab2/run-workshop-components-with-docker.md @@ -30,9 +30,9 @@ By the end of this tutorial, you can: Make sure you have: -- {{< include "nginx-one/workshops/xc-account.md" >}} +- {{< include "/nginx-one-console/workshops/xc-account.md" >}} - Docker and Docker Compose installed and running -- An active data plane key from [Lab 1: Get started with NGINX One Console]({{< ref "nginx-one/workshops/lab1/getting-started-with-nginx-one-console.md" >}}) +- An active data plane key from [Lab 1: Get started with NGINX One Console]({{< ref "/nginx-one-console/workshops/lab1/getting-started-with-nginx-one-console.md" >}}) - A trial or paid NGINX One JWT license (saved as `nginx-repo.jwt`) from [MyF5](https://my.f5.com/manage/s/) - Basic Linux and NGINX knowledge - Git installed and an SSH key set up for GitHub access @@ -150,11 +150,11 @@ Wait until you see **Started** for each container. Your containers are now up and registered with NGINX One Console. -Go to [Lab 3: Explore NGINX One Console features]({{< ref "nginx-one/workshops/lab3/explore-nginx-one-console-features.md" >}}). +Go to [Lab 3: Explore NGINX One Console features]({{< ref "/nginx-one-console/workshops/lab3/explore-nginx-one-console-features.md" >}}). --- ## References -- [NGINX One Console docs]({{< ref "/nginx-one/" >}}) -- [NGINX Agent overview]({{< ref "/nginx-one/agent/overview/about.md" >}}) +- [NGINX One Console docs]({{< ref "/nginx-one-console/" >}}) +- [NGINX Agent overview]({{< ref "/nginx-one-console/agent/overview/about.md" >}}) diff --git a/content/nginx-one/workshops/lab3/explore-nginx-one-console-features.md b/content/nginx-one-console/workshops/lab3/explore-nginx-one-console-features.md similarity index 94% rename from content/nginx-one/workshops/lab3/explore-nginx-one-console-features.md rename to content/nginx-one-console/workshops/lab3/explore-nginx-one-console-features.md index 15a50a92c..248ca2842 100644 --- a/content/nginx-one/workshops/lab3/explore-nginx-one-console-features.md +++ b/content/nginx-one-console/workshops/lab3/explore-nginx-one-console-features.md @@ -36,8 +36,8 @@ By the end of this tutorial, you can: Make sure you have: -- {{< include "nginx-one/workshops/xc-account.md" >}} -- All containers from [Lab 2: Run workshop components with Docker]({{< ref "nginx-one/workshops/lab2/run-workshop-components-with-docker.md" >}}) running and registered +- {{< include "/nginx-one-console/workshops/xc-account.md" >}} +- All containers from [Lab 2: Run workshop components with Docker]({{< ref "/nginx-one-console/workshops/lab2/run-workshop-components-with-docker.md" >}}) running and registered - {{< include "workshops/nginx-one-env-variables.md" >}} - Basic NGINX and Linux knowledge @@ -182,11 +182,11 @@ Try it on: You're ready to apply configuration changes across your fleet using sync groups. -Go to [Lab 4: Config Sync Groups]({{< ref "nginx-one/workshops/lab4/config-sync-groups.md" >}}). +Go to [Lab 4: Config Sync Groups]({{< ref "/nginx-one-console/workshops/lab4/config-sync-groups.md" >}}). --- ## References -- [NGINX One Console docs]({{< ref "nginx-one/" >}}) +- [NGINX One Console docs]({{< ref "/nginx-one-console/" >}}) - [CVE.org](https://www.cve.org/) \ No newline at end of file diff --git a/content/nginx-one/workshops/lab4/config-sync-groups.md b/content/nginx-one-console/workshops/lab4/config-sync-groups.md similarity index 96% rename from content/nginx-one/workshops/lab4/config-sync-groups.md rename to content/nginx-one-console/workshops/lab4/config-sync-groups.md index f8eab21a3..182d066ae 100644 --- a/content/nginx-one/workshops/lab4/config-sync-groups.md +++ b/content/nginx-one-console/workshops/lab4/config-sync-groups.md @@ -26,8 +26,8 @@ By the end of this lab, you can: Make sure you have: -- {{< include "nginx-one/workshops/xc-account.md" >}} -- Completed [Lab 2: Run workshop components with Docker]({{< ref "nginx-one/workshops/lab2/run-workshop-components-with-docker.md" >}}) +- {{< include "/nginx-one-console/workshops/xc-account.md" >}} +- Completed [Lab 2: Run workshop components with Docker]({{< ref "/nginx-one-console/workshops/lab2/run-workshop-components-with-docker.md" >}}) - Docker and Docker Compose installed and running - {{< include "workshops/nginx-one-env-variables.md" >}} - Basic familiarity with Linux command line and NGINX concepts @@ -192,10 +192,10 @@ Modify the shared configuration and apply the changes to all group members. You're ready to install your NGINX Plus license (JWT) on each instance. This will let you upgrade them to NGINX R34. -Go to [Lab 5: Upgrade NGINX Plus to the latest version]({{< ref "/nginx-one/workshops/lab5/upgrade-nginx-plus-to-latest-version.md" >}}). +Go to [Lab 5: Upgrade NGINX Plus to the latest version]({{< ref "/nginx-one-console/workshops/lab5/upgrade-nginx-plus-to-latest-version.md" >}}). --- ## References -- [NGINX One Console docs]({{< ref "/nginx-one/" >}}) +- [NGINX One Console docs]({{< ref "/nginx-one-console/" >}}) diff --git a/content/nginx-one/workshops/lab5/upgrade-nginx-plus-to-latest-version.md b/content/nginx-one-console/workshops/lab5/upgrade-nginx-plus-to-latest-version.md similarity index 95% rename from content/nginx-one/workshops/lab5/upgrade-nginx-plus-to-latest-version.md rename to content/nginx-one-console/workshops/lab5/upgrade-nginx-plus-to-latest-version.md index 5fc03bbc0..9e1dcdeb2 100644 --- a/content/nginx-one/workshops/lab5/upgrade-nginx-plus-to-latest-version.md +++ b/content/nginx-one-console/workshops/lab5/upgrade-nginx-plus-to-latest-version.md @@ -37,8 +37,8 @@ By the end of this lab, you can: Make sure you have: -- {{< include "nginx-one/workshops/xc-account.md" >}} -- Completed [Lab 4: Config Sync Groups]({{< ref "nginx-one/workshops/lab4/config-sync-groups.md" >}}) +- {{< include "/nginx-one-console/workshops/xc-account.md" >}} +- Completed [Lab 4: Config Sync Groups]({{< ref "/nginx-one-console/workshops/lab4/config-sync-groups.md" >}}) - Docker and Docker Compose installed and running (for Docker scenario) - A trial or paid NGINX One JWT license (saved as `nginx-repo.jwt`) from [MyF5](https://my.f5.com/manage/s/) - A VM with NGINX Plus R32 (or earlier), SSH access, and NGINX Agent installed (for VM scenario) @@ -198,11 +198,11 @@ See [About subscription licenses]({{< ref "solutions/about-subscription-licenses You have upgraded your instances to the latest NGINX Plus. -Go to the [NGINX One documentation]({{< ref "nginx-one/" >}}) for more advanced guides and use cases. +Go to the [NGINX One documentation]({{< ref "/nginx-one-console/" >}}) for more advanced guides and use cases. --- ## References -- [NGINX One Console docs]({{< ref "/nginx-one/" >}}) +- [NGINX One Console docs]({{< ref "/nginx-one-console/" >}}) - [About subscription licenses]({{< ref "solutions/about-subscription-licenses.md" >}}) diff --git a/content/nginx-one/agent/configure-instances/_index.md b/content/nginx-one/agent/configure-instances/_index.md deleted file mode 100644 index e4b8d1288..000000000 --- a/content/nginx-one/agent/configure-instances/_index.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: "Configure instances" -weight: 400 -url: /nginx-one/agent/configure-instances/ ---- \ No newline at end of file diff --git a/content/nginx-one/agent/containers/_index.md b/content/nginx-one/agent/containers/_index.md deleted file mode 100644 index d74d0a2c4..000000000 --- a/content/nginx-one/agent/containers/_index.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: "Containers" -weight: 300 -url: /nginx-one/agent/containers/ ---- \ No newline at end of file diff --git a/content/nginx-one/agent/overview/_index.md b/content/nginx-one/agent/overview/_index.md deleted file mode 100644 index b38b31aa3..000000000 --- a/content/nginx-one/agent/overview/_index.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: "Overview" -weight: 100 -url: /nginx-one/agent/overview/ ---- diff --git a/content/nginx-one/agent/support/_index.md b/content/nginx-one/agent/support/_index.md deleted file mode 100644 index 253093e5e..000000000 --- a/content/nginx-one/agent/support/_index.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: "Support" -weight: 700 -url: /nginx-one/agent/support/ ---- \ No newline at end of file diff --git a/content/nginx/admin-guide/installing-nginx/installing-nginx-docker.md b/content/nginx/admin-guide/installing-nginx/installing-nginx-docker.md index f89f8748d..6743349ae 100644 --- a/content/nginx/admin-guide/installing-nginx/installing-nginx-docker.md +++ b/content/nginx/admin-guide/installing-nginx/installing-nginx-docker.md @@ -184,7 +184,7 @@ sudo docker run \ ``` To start the Docker container with NGINX Plus and NGINX Agent, -you will need to additionally pass the NGINX One data plane key as the `NGINX_AGENT_SERVER_TOKEN` environment variable. For more information, see [Create and manage data plane keys]({{< ref "/nginx-one/connect-instances/create-manage-data-plane-keys.md" >}}): +you will need to additionally pass the NGINX One data plane key as the `NGINX_AGENT_SERVER_TOKEN` environment variable. For more information, see [Create and manage data plane keys]({{< ref "/nginx-one-console/connect-instances/create-manage-data-plane-keys.md" >}}): ```sh sudo docker run \ @@ -202,7 +202,7 @@ where: - `NGINX_LICENSE_JWT` is your JWT license file from MyF5. The file name should be `license.jwt`. - `NGINX_AGENT_SERVER_GRPCPORT` sets a GRPC port used by NGINX Agent to communicate with NGINX Instance Manager. - `NGINX_AGENT_SERVER_HOST` sets the domain name or IP address of NGINX Instance Manager. Note that for production environments it is not recommended to expose NGINX Instance Manager to public networks. - - `NGINX_AGENT_SERVER_TOKEN` sets NGINX One data plane key. See [Create and manage data plane keys]({{< ref "nginx-one/connect-instances/create-manage-data-plane-keys.md" >}}) for details. + - `NGINX_AGENT_SERVER_TOKEN` sets NGINX One data plane key. See [Create and manage data plane keys]({{< ref "/nginx-one-console/connect-instances/create-manage-data-plane-keys.md" >}}) for details. - `NGINX_AGENT_TLS_ENABLE` enables mutual TLS, server-side TLS, or insecure mode (not recommended for production environments). See [Encrypt communication]({{< ref "agent/configuration/encrypt-communication.md" >}}) for details. - `YOUR_REGISTRY` is the path to your private registry. - `VERSION_TAG` is the tag assigned when pushing to your registry. diff --git a/content/nic/changelog/_index.md b/content/nic/changelog/_index.md index 9d900288a..fcb527b44 100644 --- a/content/nic/changelog/_index.md +++ b/content/nic/changelog/_index.md @@ -106,7 +106,7 @@ We will provide technical support for NGINX Ingress Controller on any Kubernetes 08 Jul 2025 -This NGINX Ingress Controller release brings initial connectivity to the NGINX One Console! You can now use NGINX One Console to monitor NGINX instances that are part of your NGINX Ingress Controller cluster. See [here]({{< ref "/nginx-one/k8s/add-nic.md" >}}) to configure NGINX One Console with NGINX Ingress Controller. +This NGINX Ingress Controller release brings initial connectivity to the NGINX One Console! You can now use NGINX One Console to monitor NGINX instances that are part of your NGINX Ingress Controller cluster. See [here]({{< ref "/nginx-one-console/k8s/add-nic.md" >}}) to configure NGINX One Console with NGINX Ingress Controller. This release also includes the ability to configure Rate Limiting for your APIs based on a specific NGINX variable and its value. This allows you more granular control over how frequently specific users access your resources. diff --git a/content/nic/install/helm.md b/content/nic/install/helm.md index e094258ae..ae304d71a 100644 --- a/content/nic/install/helm.md +++ b/content/nic/install/helm.md @@ -305,9 +305,9 @@ The [values.schema.json](https://github.com/nginx/kubernetes-ingress/blob/main/c | **controller.enableSSLDynamicReload** | Enable lazy loading for SSL Certificates. | true | | **controller.telemetryReporting.enable** | Enable telemetry reporting. | true | | **controller.enableWeightChangesDynamicReload** | Enable weight changes without reloading the NGINX configuration. May require increasing `map_hash_bucket_size`, `map_hash_max_size`, `variable_hash_bucket_size`, and `variable_hash_max_size` in the [ConfigMap]({{< ref "/nic/configuration/global-configuration/configmap-resource.md" >}}) if there are many two-way splits. Requires `controller.nginxplus` | false | -|**nginxAgent.enable** | Enable NGINX Agent 3.x to allow [connecting to NGINX One Console]({{< ref "/nginx-one/k8s/add-nic.md" >}}) or to integrate NGINX Agent 2.x for [Security Monitoring]({{< ref "/nic/tutorials/security-monitoring.md" >}}) . | false | +|**nginxAgent.enable** | Enable NGINX Agent 3.x to allow [connecting to NGINX One Console]({{< ref "/nginx-one-console/k8s/add-nic.md" >}}) or to integrate NGINX Agent 2.x for [Security Monitoring]({{< ref "/nic/tutorials/security-monitoring.md" >}}) . | false | |**nginxAgent.logLevel** | Log level for NGINX Agent. | "error" | -|**nginxAgent.dataplaneKeySecretName** | Name of the Kubernetes Secret containing the Data Plane key used to authenticate to NGINX One Console. Learn more [here]({{< ref "/nginx-one/k8s/add-nic.md" >}}). Required when `nginxAgent.enable` is set to `true`. Requires NGINX Agent 3.x. | "" | +|**nginxAgent.dataplaneKeySecretName** | Name of the Kubernetes Secret containing the Data Plane key used to authenticate to NGINX One Console. Learn more [here]({{< ref "/nginx-one-console/k8s/add-nic.md" >}}). Required when `nginxAgent.enable` is set to `true`. Requires NGINX Agent 3.x. | "" | |**nginxAgent.endpointHost** | Domain or IP address for the NGINX One Console. Requires NGINX Agent 3.x. | "agent.connect.nginx.com" | |**nginxAgent.endpointPort** | Port for the NGINX One Console endpoint. Requires NGINX Agent 3.x. | 443 | |**nginxAgent.tlsSkipVerify** | Skip TLS verification for the NGINX One Console endpoint. Requires NGINX Agent 3.x. | false | diff --git a/content/nim/_index.md b/content/nim/_index.md index ff31e0d96..6d9f4bd96 100644 --- a/content/nim/_index.md +++ b/content/nim/_index.md @@ -84,7 +84,7 @@ NGINX Instance Manager is part of NGINX One, which includes [NGINX One component {{}} {{}} {{< card-section title="Cloud Console Option">}} - {{< card title="NGINX One Console" titleUrl="/nginx-one/" brandIcon="NGINX-One-product-icon.svg">}} + {{< card title="NGINX One Console" titleUrl="/nginx-one-console/" brandIcon="NGINX-One-product-icon.svg">}} Manage, monitor, and secure your NGINX fleet from a centralized web-based interface. {{}} {{}} diff --git a/content/nim/nginx-instances/manage-instance-groups.md b/content/nim/nginx-instances/manage-instance-groups.md index fb03684dc..9f52f6706 100644 --- a/content/nim/nginx-instances/manage-instance-groups.md +++ b/content/nim/nginx-instances/manage-instance-groups.md @@ -62,7 +62,7 @@ You can assign NGINX instances to instance groups in the following ways: ### Specify Instance Group in Agent-Dynamic.Conf -You can easily add instances to a default instance group that you specify. To do so, [install the NGINX Agent on an instance]({{< ref "/nginx-one/agent/install-upgrade/" >}}), then edit the `/var/lib/nginx-agent/agent-dynamic.conf` file as described below. +You can easily add instances to a default instance group that you specify. To do so, [install the NGINX Agent on an instance]({{< ref "/nginx-one-console/agent/install-upgrade/" >}}), then edit the `/var/lib/nginx-agent/agent-dynamic.conf` file as described below. {{< call-out "note" >}}If you're running Instance Manager 2.10.1 or earlier or NGINX Agent 2.25.1 or earlier, the `agent-dynamic.conf` file is located in `/etc/nginx-agent/`.{{< /call-out >}} diff --git a/content/nim/releases/release-notes.md b/content/nim/releases/release-notes.md index 5de669873..ada5ba8ae 100644 --- a/content/nim/releases/release-notes.md +++ b/content/nim/releases/release-notes.md @@ -1130,7 +1130,7 @@ This release includes the following security updates: #### Mitigation - - Avoid configuring trace-level logging in the NGINX Agent configuration file. For more information, refer to the [Configuring the NGINX Agent]({{< ref "/nginx-one/agent/configure-instances/configuration-overview/">}} section of the documentation. If trace-level logging is required, ensure only trusted users have access to the log files. + - Avoid configuring trace-level logging in the NGINX Agent configuration file. For more information, refer to the [Configuring the NGINX Agent]({{< ref "/nginx-one-console/agent/configure-instances/configuration-overview/">}} section of the documentation. If trace-level logging is required, ensure only trusted users have access to the log files. #### Fixed in diff --git a/content/solutions/about-subscription-licenses/getting-started.md b/content/solutions/about-subscription-licenses/getting-started.md index 7d3374bc0..3ac87172f 100644 --- a/content/solutions/about-subscription-licenses/getting-started.md +++ b/content/solutions/about-subscription-licenses/getting-started.md @@ -53,7 +53,7 @@ Processing traffic requires: After you download the JWT license, deploy it to your NGINX Plus instances in one of two ways: - **Use a group sync feature (recommended):** - - In the [NGINX One Console]({{< ref "/nginx-one/getting-started.md" >}}), use a **Config Sync Group** to keep instances consistent, avoid manual copying, and apply license updates automatically. + - In the [NGINX One Console]({{< ref "/nginx-one-console/getting-started.md" >}}), use a **Config Sync Group** to keep instances consistent, avoid manual copying, and apply license updates automatically. - In [NGINX Instance Manager]({{< ref "/nim/nginx-instances/manage-instance-groups.md" >}}), use an **instance group**, which works the same way as a Config Sync Group. - **Copy the license manually:** Place the license file on each NGINX Plus instance yourself. diff --git a/static/nginx-one/api/one.json b/static/nginx-one/api/one.json index 3440c9564..8547c3fff 100644 --- a/static/nginx-one/api/one.json +++ b/static/nginx-one/api/one.json @@ -4071,7 +4071,7 @@ "x-nginx-one-action": "export", "x-nginx-one-entity": "NGINX staged config", "summary": "Export staged configuration", - "description": "Exports staged configuration as a gzipped tar archive. Does not include sensitive data such as SSL certificates. [Learn more](https://docs.nginx.com/nginx-one/how-to/staged-configs/import-export-staged-config/).\n", + "description": "Exports staged configuration as a gzipped tar archive. Does not include sensitive data such as SSL certificates. [Learn more](https://docs.nginx.com/nginx-one-console/nginx-configs/staged-configs/import-export-staged-config/).\n", "operationId": "exportStagedConfig", "responses": { "200": {