docs: add missing NIC docs to the catalog (#764)

Author: JTorreG

content/nic/configuration/access-control.md

@@ -2,7 +2,7 @@
 title: Deploy a Policy for access control
 weight: 900
 toc: true
-docs: DOCS-000
+nd-docs: DOCS-1858
 ---
 
 This topic describes how to use F5 NGINX Ingress Controller to apply and update a Policy for access control. It demonstrates it using an example application and a [VirtualServer custom resource]({{< ref "/nic/configuration/virtualserver-and-virtualserverroute-resources.md" >}}).

content/nic/configuration/configuration-examples.md

@@ -1,5 +1,5 @@
 ---
-docs: DOCS-584
+nd-docs: DOCS-584
 doctypes:
 - ''
 title: Configuration examples

content/nic/configuration/global-configuration/command-line-arguments.md

@@ -1,5 +1,5 @@
 ---
-docs: DOCS-585
+nd-docs: DOCS-585
 doctypes:
 - ''
 title: Command-line arguments

content/nic/configuration/global-configuration/configmap-resource.md

@@ -184,12 +184,12 @@ For more information, view the [VirtualServer and VirtualServerRoute resources](
 
 Zone Sync enables the [ngx_stream_zone_sync_module](https://nginx.org/en/docs/stream/ngx_stream_zone_sync_module.html) in NGINX Ingress Controller when NGINX Plus is used.  Multiple replicas are required to effectively utililise this functionality. More information is available in the [How NGINX Plus Performs Zone Synchronization]({{< ref "/nginx/admin-guide/high-availability/zone_sync_details.md" >}}) topic.
 
-Zone synchronization with TLS for NGINX Ingress Controller is not yet available with ConfigMap. If you would like to enable Zone Sync with TLS, please remove `zone-sync` from ConfigMap and add Zone Sync parameters via [`stream-snippets`]({{< ref "/nic/configuration/ingress-resources/advanced-configuration-with-snippets.md" >}}) similar to [this example](https://github.com/nginx/kubernetes-ingress/blob/v4.0.1/examples/custom-resources/oidc/nginx-config.yaml) and adding the [zone_sync_ssl directive](https://nginx.org/en/docs/stream/ngx_stream_zone_sync_module.html#zone_sync_ssl) along with any other TLS parameters to the `stream-snippets`. 
+Zone synchronization with TLS for NGINX Ingress Controller is not yet available with ConfigMap. If you would like to enable Zone Sync with TLS, please remove `zone-sync` from ConfigMap and add Zone Sync parameters via [`stream-snippets`]({{< ref "/nic/configuration/ingress-resources/advanced-configuration-with-snippets.md" >}}) similar to [this example](https://github.com/nginx/kubernetes-ingress/blob/v4.0.1/examples/custom-resources/oidc/nginx-config.yaml) and adding the [zone_sync_ssl directive](https://nginx.org/en/docs/stream/ngx_stream_zone_sync_module.html#zone_sync_ssl) along with any other TLS parameters to the `stream-snippets`.
 
 You will also need to manually add the headless service, such as in [this example](https://github.com/nginx/kubernetes-ingress/blob/v4.0.1/examples/custom-resources/oidc/nginx-ingress-headless.yaml).
 
-{{< caution >}} 
-If you previously installed OIDC or used the `zone_sync` directive with `stream-snippets` in [v4.0.1](https://github.com/nginx/kubernetes-ingress/tree/v4.0.1) or earlier, and you plan to enable the `zone-sync` ConfigMap key, the `zone_sync` directive should be removed from `stream-snippets`. 
+{{< caution >}}
+If you previously installed OIDC or used the `zone_sync` directive with `stream-snippets` in [v4.0.1](https://github.com/nginx/kubernetes-ingress/tree/v4.0.1) or earlier, and you plan to enable the `zone-sync` ConfigMap key, the `zone_sync` directive should be removed from `stream-snippets`.
 
 If you encounter the error `error [emerg] 13#13: "zone_sync" directive is duplicate in /etc/nginx/nginx.conf:164` it is likely due to `zone_sync` being enabled in both `stream-snippets` and the ConfigMap. Once upgraded, remove the [old headless service](https://github.com/nginx/kubernetes-ingress/blob/v4.0.1/examples/custom-resources/oidc/nginx-ingress-headless.yaml) deployed for OIDC.
 {{< /caution >}}

content/nic/configuration/global-configuration/custom-templates.md

@@ -1,5 +1,5 @@
 ---
-docs: DOCS-587
+nd-docs: DOCS-587
 doctypes:
 - ''
 title: Custom templates

content/nic/configuration/global-configuration/globalconfiguration-resource.md

@@ -1,5 +1,5 @@
 ---
-docs: DOCS-588
+nd-docs: DOCS-588
 doctypes:
 - ''
 title: GlobalConfiguration resource

content/nic/configuration/global-configuration/mgmt-configmap-resource.md

@@ -1,13 +1,13 @@
 ---
-docs: DOCS-586
+nd-docs: DOCS-1859
 doctypes:
 - ''
 title: Management ConfigMap resource
 toc: true
 weight: 300
 ---
 
-When using F5 NGINX Ingress Controller with NGINX Plus, it is required to pass a [command line argument]({{< ref "/nic/configuration/global-configuration/command-line-arguments" >}}) to NGINX Ingress Controller, `--mgmt-configmap=<namespace/name>` which specifies the ConfigMap to use. The minimal required ConfigMap must have a `license-token-secret-name` key. Helm users will not need to create this map or pass the argument, it will be created with a Helm install. 
+When using F5 NGINX Ingress Controller with NGINX Plus, it is required to pass a [command line argument]({{< ref "/nic/configuration/global-configuration/command-line-arguments" >}}) to NGINX Ingress Controller, `--mgmt-configmap=<namespace/name>` which specifies the ConfigMap to use. The minimal required ConfigMap must have a `license-token-secret-name` key. Helm users will not need to create this map or pass the argument, it will be created with a Helm install.
 
 ---
 

content/nic/configuration/host-and-listener-collisions.md

@@ -2,7 +2,7 @@
 title: Host and Listener collisions
 toc: true
 weight: 800
-docs: DOCS-590
+nd-docs: DOCS-590
 ---
 
 This document explains how F5 NGINX Ingress Controller handles host and listener collisions between resources.

content/nic/configuration/ingress-resources/advanced-configuration-with-snippets.md

@@ -1,15 +1,15 @@
 ---
-docs: DOCS-592
+nd-docs: DOCS-592
 doctypes:
 - ''
 title: Advanced configuration with Snippets
 toc: true
 weight: 400
 ---
 
-Snippets allow you to insert raw NGINX config into different contexts of the NGINX configurations that F5 NGINX Ingress Controller generates. 
+Snippets allow you to insert raw NGINX config into different contexts of the NGINX configurations that F5 NGINX Ingress Controller generates.
 
-Snippets are intended for advanced NGINX users who need more control over the generated NGINX configuration, and can be used in cases where Annotations and ConfigMap entries would not apply. 
+Snippets are intended for advanced NGINX users who need more control over the generated NGINX configuration, and can be used in cases where Annotations and ConfigMap entries would not apply.
 
 
 
@@ -27,7 +27,7 @@ Snippets have the following disadvantages:
 - *Decreased robustness*. An incorrect snippet can invalidate NGINX configuration, causing reload failures. Until the snippet is fixed, it will prevent any new configuration updates, including updates for the other Ingress resources.
 - *Security implications*. Snippets give access to NGINX configuration primitives, which are not validated by NGINX Ingress Controller. For example, a snippet can configure NGINX to serve the TLS certificates and keys used for TLS termination for Ingress resources.
 
-{{< note >}} If the NGINX configuration includes an invalid snippet, NGINX will continue to operate with the last valid configuration. {{< /note >}} 
+{{< note >}} If the NGINX configuration includes an invalid snippet, NGINX will continue to operate with the last valid configuration. {{< /note >}}
 
 ## Using snippets
 
@@ -68,7 +68,7 @@ spec:
 
 These snippets generate the following NGINX configuration:
 
-{{< note >}} The example is shortened for conciseness. {{< /note >}} 
+{{< note >}} The example is shortened for conciseness. {{< /note >}}
 
 ```nginx
 server {

content/nic/configuration/ingress-resources/basic-configuration.md

@@ -4,7 +4,7 @@ weight: 100
 toc: true
 type: reference
 product: NIC
-docs: DOCS-593
+nd-docs: DOCS-593
 ---
 
 This document shows a basic Ingress resource definition for F5 NGINX Ingress Controller. It load balances requests for two services as part of a single application.
@@ -93,9 +93,9 @@ NGINX Ingress Controller imposes the following restrictions on Ingress resources
 
 ## Advanced configuration
 
-NGINX Ingress Controller generates NGINX configuration by executing a template file that contains the configuration options. 
+NGINX Ingress Controller generates NGINX configuration by executing a template file that contains the configuration options.
 
-These options are set with the Ingress resource and NGINX Ingress Controller's ConfigMap.  
+These options are set with the Ingress resource and NGINX Ingress Controller's ConfigMap.
 
 The Ingress resource only allows you to use basic NGINX features: host and path-based routing and TLS termination.