From acb1a57ad8b47019b6194c4f97fc01dae2d423ad Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Thu, 26 Jun 2025 16:51:49 +0530 Subject: [PATCH 01/27] fix: Added instruction to install NIM 2.19.0 --- .../deploy/kubernetes/deploy-using-helm.md | 123 ++++++++++++++++-- 1 file changed, 112 insertions(+), 11 deletions(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index dab74919c..6492fe4c0 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -149,37 +149,37 @@ imagePullSecrets: apigw: image: repository: private-registry.nginx.com/nms/apigw - tag: 2.20.0 + tag: core: image: repository: private-registry.nginx.com/nms/core - tag: 2.20.0 + tag: dpm: image: repository: private-registry.nginx.com/nms/dpm - tag: 2.20.0 + tag: ingestion: image: repository: private-registry.nginx.com/nms/ingestion - tag: 2.20.0 + tag: integrations: image: repository: private-registry.nginx.com/nms/integrations - tag: 2.20.0 + tag: secmon: image: repository: private-registry.nginx.com/nms/secmon - tag: 2.20.0 + tag: utility: image: repository: private-registry.nginx.com/nms/utility - tag: 2.20.0 + tag: ``` These values are required when pulling images from the NGINX private registry. The chart does not auto-resolve image tags. Update the tag: fields to match the NGINX Instance Manager version you want to install. @@ -236,6 +236,11 @@ helm status nim -n nim You should see `STATUS: deployed` in the output. + +To help you choose the right NGINX Instance Manager chart version, see the table in: + +{{< include "nim/kubernetes/nms-chart-supported-module-versions.md" >}} + --- ## Access the web interface @@ -346,6 +351,106 @@ networkPolicies: --- +## Helm Deployment for NGINX Instance Manager 2.19 + +### Create a Helm deployment values.yaml file + +The `values.yaml` file customizes the Helm chart installation without modifying the chart itself. You can use it to specify image repositories, environment variables, resource requests, and other settings. + +1. Create a `values.yaml` file similar to this example: + + - In the `imagePullSecrets` section, add the credentials for your private Docker registry. + - Change the version tag to the version of NGINX Instance Manager you would like to install. See "Install the chart" below for versions. + + {{< see-also >}} For details on creating a secret, see Kubernetes [Pull an Image from a Private Registry](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/). {{}} + + ```yaml + imagePullSecrets: + - name: regcred + apigw: + image: + repository: private-registry.nginx.com/nms/apigw + tag: + core: + image: + repository: private-registry.nginx.com/nms/core + tag: + dpm: + image: + repository: private-registry.nginx.com/nms/dpm + tag: + ingestion: + image: + repository: private-registry.nginx.com/nms/ingestion + tag: + integrations: + image: + repository: private-registry.nginx.com/nms/integrations + tag: + utility: + image: + repository: private-registry.nginx.com/nms/utility + tag: + ``` + +2. Save and close the `values.yaml` file. + +--- + +### Install the chart + +Run the `helm install` command to deploy NGINX Instance Manager: + +1. Replace `` with the path to your `values.yaml` file. +2. Replace `YourPassword123#` with a secure password (containing a mix of uppercase, lowercase letters, numbers, and special characters). + + {{< important >}} Remember to save the password for future use. Only the encrypted password is stored, and there's no way to recover or reset it if lost. {{< /important >}} + + +```shell +helm install -n nms-hybrid \ +--set adminPasswordHash=$(openssl passwd -6 'YourPassword123#') \ +nms nginx-stable/nms-hybrid \ +--create-namespace \ +-f \ +--version \ +--wait +``` + +--- + +### Upgrade NGINX Instance Manager + +To upgrade: + +1. [Update the Helm repository list](#add-repository). +2. [Adjust your `values.yaml` file](#create-a-helm-deployment-values.yaml-file) if needed. +3. To upgrade the NGINX Instance Manager deployment, run the following command. This command updates the `nms` deployment with a new version from the `nginx-stable/nms-hybrid` repository. It also hashes the provided password and uses the `values.yaml` file at the path you specify. +4. Replace `` with the desired chart version of NGINX Instance Manager 2.19 referring the helm chart table. + + ```shell + helm upgrade -n nms \ + --set nms-hybrid.adminPasswordHash=$(openssl passwd -6 'YourPassword123#') \ + nms nginx-stable/nms-hybrid \ + -f \ + --version \ + --wait + ``` + + - Replace `` with the path to the `values.yaml` file you created]({{< ref "/nim/deploy/kubernetes/deploy-using-helm.md#configure-chart" >}}). + - Replace `YourPassword123#` with a secure password that includes uppercase and lowercase letters, numbers, and special characters. + + {{}} Save this password for future use. Only the encrypted password is stored in Kubernetes, and you can’t recover or reset it later. {{}} + +{{< call-out "note" "Upgrading from 2.18.0 or lower to 2.19" >}} +If you’re upgrading from a deployment that used the legacy `nms` chart or release name, you’ll need to update the chart reference and adjust the release name as needed. +The structure of values.yaml is different from previous releases. +{{< /call-out >}} + +--- + +--- + ## Helm Deployment for NGINX Instance Manager 2.18 or lower ### Create a Helm deployment values.yaml file @@ -414,10 +519,6 @@ nms nginx-stable/nms \ --wait ``` -To help you choose the right NGINX Instance Manager chart version, see the table in: - -{{< include "nim/kubernetes/nms-chart-supported-module-versions.md" >}} - --- ### Upgrade NGINX Instance Manager From bf85f17f324f09e2afecf4203ff3f47078d68714 Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Thu, 26 Jun 2025 17:06:38 +0530 Subject: [PATCH 02/27] fix: minor fixes --- .../deploy/kubernetes/deploy-using-helm.md | 24 +++++++++---------- 1 file changed, 11 insertions(+), 13 deletions(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index 6492fe4c0..1efa93087 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -149,40 +149,40 @@ imagePullSecrets: apigw: image: repository: private-registry.nginx.com/nms/apigw - tag: + tag: core: image: repository: private-registry.nginx.com/nms/core - tag: + tag: dpm: image: repository: private-registry.nginx.com/nms/dpm - tag: + tag: ingestion: image: repository: private-registry.nginx.com/nms/ingestion - tag: + tag: integrations: image: repository: private-registry.nginx.com/nms/integrations - tag: + tag: secmon: image: repository: private-registry.nginx.com/nms/secmon - tag: + tag: utility: image: repository: private-registry.nginx.com/nms/utility - tag: + tag: ``` -These values are required when pulling images from the NGINX private registry. The chart does not auto-resolve image tags. Update the tag: fields to match the NGINX Instance Manager version you want to install. +These values are required when pulling images from the NGINX private registry. The chart does not auto-resolve image tags. Update the tag: fields to match the NGINX Instance Manager version you want to install referring the helm chart table. Use the file with the `-f values.yaml` flag when installing the chart. @@ -360,7 +360,7 @@ The `values.yaml` file customizes the Helm chart installation without modifying 1. Create a `values.yaml` file similar to this example: - In the `imagePullSecrets` section, add the credentials for your private Docker registry. - - Change the version tag to the version of NGINX Instance Manager you would like to install. See "Install the chart" below for versions. + - Change the version tag to the version of NGINX Instance Manager you would like to install. Refer helm chart table for versions. {{< see-also >}} For details on creating a secret, see Kubernetes [Pull an Image from a Private Registry](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/). {{}} @@ -426,7 +426,7 @@ To upgrade: 1. [Update the Helm repository list](#add-repository). 2. [Adjust your `values.yaml` file](#create-a-helm-deployment-values.yaml-file) if needed. 3. To upgrade the NGINX Instance Manager deployment, run the following command. This command updates the `nms` deployment with a new version from the `nginx-stable/nms-hybrid` repository. It also hashes the provided password and uses the `values.yaml` file at the path you specify. -4. Replace `` with the desired chart version of NGINX Instance Manager 2.19 referring the helm chart table. +4. Replace `` with the desired chart version of NGINX Instance Manager 2.19.x referring the helm chart table. ```shell helm upgrade -n nms \ @@ -442,15 +442,13 @@ To upgrade: {{}} Save this password for future use. Only the encrypted password is stored in Kubernetes, and you can’t recover or reset it later. {{}} -{{< call-out "note" "Upgrading from 2.18.0 or lower to 2.19" >}} +{{< call-out "note" "Upgrading from 2.18.0 or lower to 2.19.x" >}} If you’re upgrading from a deployment that used the legacy `nms` chart or release name, you’ll need to update the chart reference and adjust the release name as needed. The structure of values.yaml is different from previous releases. {{< /call-out >}} --- ---- - ## Helm Deployment for NGINX Instance Manager 2.18 or lower ### Create a Helm deployment values.yaml file From 6536bdcc2b9a732a6a72898d01815c3ca5105280 Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Fri, 27 Jun 2025 15:28:29 +0530 Subject: [PATCH 03/27] fix: call out about the new helm chart versioning --- content/nim/deploy/kubernetes/deploy-using-helm.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index 1efa93087..2fc36891a 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -22,6 +22,10 @@ The Helm chart has been renamed from `nginx-stable/nms-hybrid` to `nginx-stable/ Make sure to update your chart references if you’re using version 2.20.0 or later. {{< /call-out >}} +{{< call-out "note" "Versioning update from NIM 2.20.0" >}} +With the chart rename in NIM 2.20.0, Helm chart versioning was also reset—`v2.0.0` is the first release under the new nginx-stable/nim chart name. +{{< /call-out >}} + --- From 8d91945845f5c6f5283d985d7bb54d0869a13579 Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Mon, 30 Jun 2025 16:38:36 +0530 Subject: [PATCH 04/27] fix: added openshift details in nim k8s docs --- content/nim/deploy/kubernetes/deploy-using-helm.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index 2fc36891a..ab5ddb712 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -565,6 +565,14 @@ openshift: This ensures pods can run with the user IDs required by NGINX Instance Manager services. +{{< note >}} The NIM deployment on OpenShift has been tested with OpenShift v4.13.0 Server. {{< /note >}} + +### How OpenShift handles security constraints + +When `openshift.enabled: true` is set in the `values.yaml` file, the NGINX Instance Manager deployment automatically creates a **custom [Security Context Constraints](https://docs.redhat.com/en/documentation/openshift_container_platform/4.13/html/authentication_and_authorization/managing-pod-security-policies) (SCCs)** and links it to the Service Account used by all pods. + +By default, OpenShift enforces strict security policies that require containers to run as **non-root** users. The NGINX Instance Manager deployment needs specific user IDs (UIDs) for certain services, such as **1000** for `nms` and **101** for `nginx` and `clickhouse`. Since the default SCCs do not allow these UIDs, a **custom SCC** is created. This ensures that the deployment can run with the necessary permissions while maintaining OpenShift’s security standards. The custom SCC allows these UIDs by setting the `runAsUser` field, which controls which users can run containers. + {{< call-out "note" "Note" >}} If you see permission errors during deployment, your user account might not have access to manage SCCs. Contact a cluster administrator to request access. {{< /call-out >}} From 0da59e1d22c37f9b91f6497868e93b7164a70b9d Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Mon, 30 Jun 2025 16:47:47 +0530 Subject: [PATCH 05/27] fix: minor changes --- content/nim/deploy/kubernetes/deploy-using-helm.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index ab5ddb712..5356ab347 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -565,17 +565,13 @@ openshift: This ensures pods can run with the user IDs required by NGINX Instance Manager services. -{{< note >}} The NIM deployment on OpenShift has been tested with OpenShift v4.13.0 Server. {{< /note >}} - -### How OpenShift handles security constraints When `openshift.enabled: true` is set in the `values.yaml` file, the NGINX Instance Manager deployment automatically creates a **custom [Security Context Constraints](https://docs.redhat.com/en/documentation/openshift_container_platform/4.13/html/authentication_and_authorization/managing-pod-security-policies) (SCCs)** and links it to the Service Account used by all pods. By default, OpenShift enforces strict security policies that require containers to run as **non-root** users. The NGINX Instance Manager deployment needs specific user IDs (UIDs) for certain services, such as **1000** for `nms` and **101** for `nginx` and `clickhouse`. Since the default SCCs do not allow these UIDs, a **custom SCC** is created. This ensures that the deployment can run with the necessary permissions while maintaining OpenShift’s security standards. The custom SCC allows these UIDs by setting the `runAsUser` field, which controls which users can run containers. -{{< call-out "note" "Note" >}} -If you see permission errors during deployment, your user account might not have access to manage SCCs. Contact a cluster administrator to request access. -{{< /call-out >}} +{{< note >}} The NIM deployment on OpenShift has been tested with OpenShift v4.13.0 Server. {{< /note >}} +{{< note >}} If you see permission errors during deployment, your user account might not have access to manage SCCs. Contact a cluster administrator to request access. {{< /note >}} To verify that the SCC was created after installing the Helm chart, run: From 156ce84092696618cadf6ff4789ca1e5a6470463 Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Mon, 30 Jun 2025 17:59:27 +0530 Subject: [PATCH 06/27] Update content/nim/deploy/kubernetes/deploy-using-helm.md Co-authored-by: Jon Torre <78599298+JTorreG@users.noreply.github.com> --- content/nim/deploy/kubernetes/deploy-using-helm.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index 5356ab347..65a6f3f32 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -22,8 +22,8 @@ The Helm chart has been renamed from `nginx-stable/nms-hybrid` to `nginx-stable/ Make sure to update your chart references if you’re using version 2.20.0 or later. {{< /call-out >}} -{{< call-out "note" "Versioning update from NIM 2.20.0" >}} -With the chart rename in NIM 2.20.0, Helm chart versioning was also reset—`v2.0.0` is the first release under the new nginx-stable/nim chart name. +{{< call-out "note" "Versioning update from NGINX Instance Manager 2.20.0" >}} +Helm chart versioning was reset with the chart rename in NGINX Instance Manager 2.20.0; `v2.0.0` is the first release under the new nginx-stable/nim chart name. {{< /call-out >}} From b3e8bd46abe6b9418e2c7ecace6a828f4f280210 Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Mon, 30 Jun 2025 17:59:40 +0530 Subject: [PATCH 07/27] Update content/nim/deploy/kubernetes/deploy-using-helm.md Co-authored-by: Jon Torre <78599298+JTorreG@users.noreply.github.com> --- content/nim/deploy/kubernetes/deploy-using-helm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index 65a6f3f32..124e70dbe 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -186,7 +186,7 @@ utility: tag: ``` -These values are required when pulling images from the NGINX private registry. The chart does not auto-resolve image tags. Update the tag: fields to match the NGINX Instance Manager version you want to install referring the helm chart table. +These values are required when pulling images from the NGINX private registry. The chart does not auto-resolve image tags. Update the tag: fields to match the NGINX Instance Manager version you want to install referring the Helm chart table. Use the file with the `-f values.yaml` flag when installing the chart. From 5a7f3b4dbf125c30851262cb760f8c559c4b2508 Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Mon, 30 Jun 2025 17:59:53 +0530 Subject: [PATCH 08/27] Update content/nim/deploy/kubernetes/deploy-using-helm.md Co-authored-by: Jon Torre <78599298+JTorreG@users.noreply.github.com> --- content/nim/deploy/kubernetes/deploy-using-helm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index 124e70dbe..28810fd57 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -241,7 +241,7 @@ helm status nim -n nim You should see `STATUS: deployed` in the output. -To help you choose the right NGINX Instance Manager chart version, see the table in: +To help you choose the right NGINX Instance Manager chart version, see the following table: {{< include "nim/kubernetes/nms-chart-supported-module-versions.md" >}} From 98fa2a625f7e5090acea56b9bafc7ba8e949083f Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Mon, 30 Jun 2025 18:01:11 +0530 Subject: [PATCH 09/27] Update content/nim/deploy/kubernetes/deploy-using-helm.md Co-authored-by: Jon Torre <78599298+JTorreG@users.noreply.github.com> --- content/nim/deploy/kubernetes/deploy-using-helm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index 28810fd57..9f5d15510 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -355,7 +355,7 @@ networkPolicies: --- -## Helm Deployment for NGINX Instance Manager 2.19 +## Helm deployment for NGINX Instance Manager 2.19 ### Create a Helm deployment values.yaml file From c5a182db2f6b0d7e045e18f29df758db93114b12 Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Mon, 30 Jun 2025 18:01:28 +0530 Subject: [PATCH 10/27] Update content/nim/deploy/kubernetes/deploy-using-helm.md Co-authored-by: Jon Torre <78599298+JTorreG@users.noreply.github.com> --- content/nim/deploy/kubernetes/deploy-using-helm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index 9f5d15510..53aefe80a 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -366,7 +366,7 @@ The `values.yaml` file customizes the Helm chart installation without modifying - In the `imagePullSecrets` section, add the credentials for your private Docker registry. - Change the version tag to the version of NGINX Instance Manager you would like to install. Refer helm chart table for versions. - {{< see-also >}} For details on creating a secret, see Kubernetes [Pull an Image from a Private Registry](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/). {{}} + {{< see-also >}} For details on creating a secret, see the Kubernetes [Pull an Image from a Private Registry](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/) documentation. {{}} ```yaml imagePullSecrets: From d5de95c0d435e94fafe92ec4722111f7a5e42928 Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Mon, 30 Jun 2025 18:01:51 +0530 Subject: [PATCH 11/27] Update content/nim/deploy/kubernetes/deploy-using-helm.md Co-authored-by: Jon Torre <78599298+JTorreG@users.noreply.github.com> --- content/nim/deploy/kubernetes/deploy-using-helm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index 53aefe80a..ee0653adc 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -570,7 +570,7 @@ When `openshift.enabled: true` is set in the `values.yaml` file, the NGINX Insta By default, OpenShift enforces strict security policies that require containers to run as **non-root** users. The NGINX Instance Manager deployment needs specific user IDs (UIDs) for certain services, such as **1000** for `nms` and **101** for `nginx` and `clickhouse`. Since the default SCCs do not allow these UIDs, a **custom SCC** is created. This ensures that the deployment can run with the necessary permissions while maintaining OpenShift’s security standards. The custom SCC allows these UIDs by setting the `runAsUser` field, which controls which users can run containers. -{{< note >}} The NIM deployment on OpenShift has been tested with OpenShift v4.13.0 Server. {{< /note >}} +{{< note >}} The NGINX Instance Manager deployment on OpenShift has been tested with OpenShift v4.13.0 Server. {{< /note >}} {{< note >}} If you see permission errors during deployment, your user account might not have access to manage SCCs. Contact a cluster administrator to request access. {{< /note >}} To verify that the SCC was created after installing the Helm chart, run: From f9bcbf56d78042e30e73af7b290b0721ba0487c2 Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Mon, 30 Jun 2025 18:01:57 +0530 Subject: [PATCH 12/27] Update content/nim/deploy/kubernetes/deploy-using-helm.md Co-authored-by: Jon Torre <78599298+JTorreG@users.noreply.github.com> --- content/nim/deploy/kubernetes/deploy-using-helm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index ee0653adc..3618a830e 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -430,7 +430,7 @@ To upgrade: 1. [Update the Helm repository list](#add-repository). 2. [Adjust your `values.yaml` file](#create-a-helm-deployment-values.yaml-file) if needed. 3. To upgrade the NGINX Instance Manager deployment, run the following command. This command updates the `nms` deployment with a new version from the `nginx-stable/nms-hybrid` repository. It also hashes the provided password and uses the `values.yaml` file at the path you specify. -4. Replace `` with the desired chart version of NGINX Instance Manager 2.19.x referring the helm chart table. +4. Replace `` with the desired chart version of NGINX Instance Manager 2.19.x referring the Helm chart table. ```shell helm upgrade -n nms \ From beb0ba2fd80fff1bcaab0a1694c67b92b5ad6f36 Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Mon, 30 Jun 2025 18:02:11 +0530 Subject: [PATCH 13/27] Update content/nim/deploy/kubernetes/deploy-using-helm.md Co-authored-by: Jon Torre <78599298+JTorreG@users.noreply.github.com> --- content/nim/deploy/kubernetes/deploy-using-helm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index 3618a830e..de9570ba3 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -364,7 +364,7 @@ The `values.yaml` file customizes the Helm chart installation without modifying 1. Create a `values.yaml` file similar to this example: - In the `imagePullSecrets` section, add the credentials for your private Docker registry. - - Change the version tag to the version of NGINX Instance Manager you would like to install. Refer helm chart table for versions. + - Change the version tag to the version of NGINX Instance Manager you would like to install. Refer Helm chart table for versions. {{< see-also >}} For details on creating a secret, see the Kubernetes [Pull an Image from a Private Registry](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/) documentation. {{}} From ff6f7bfdac652ebc6619c7637dd39c4fe6b450c0 Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Mon, 30 Jun 2025 18:41:51 +0530 Subject: [PATCH 14/27] fix: Update deploy-using-helm.md --- content/nim/deploy/kubernetes/deploy-using-helm.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index de9570ba3..9626f347f 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -395,6 +395,10 @@ The `values.yaml` file customizes the Helm chart installation without modifying image: repository: private-registry.nginx.com/nms/utility tag: + secmon: + image: + repository: private-registry.nginx.com/nms/secmon + tag: ``` 2. Save and close the `values.yaml` file. From ebd3ee09aa0ffb3a464136363d7943dbafb7182f Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Mon, 30 Jun 2025 20:30:36 +0530 Subject: [PATCH 15/27] fix: Update deploy-using-helm.md --- content/nim/deploy/kubernetes/deploy-using-helm.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index 9626f347f..f5ec50f09 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -391,14 +391,14 @@ The `values.yaml` file customizes the Helm chart installation without modifying image: repository: private-registry.nginx.com/nms/integrations tag: - utility: - image: - repository: private-registry.nginx.com/nms/utility - tag: secmon: image: repository: private-registry.nginx.com/nms/secmon tag: + utility: + image: + repository: private-registry.nginx.com/nms/utility + tag: ``` 2. Save and close the `values.yaml` file. From 9c95c078e38ae5f6cc6cede9f8401eaa9e18cf3a Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Tue, 1 Jul 2025 14:17:14 +0530 Subject: [PATCH 16/27] fix: combined call-out of renaming and versioning --- content/nim/deploy/kubernetes/deploy-using-helm.md | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index f5ec50f09..46233a780 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -17,13 +17,8 @@ Starting with version 2.20.0, NGINX Instance Manager supports **lightweight mode - Lightweight mode requires NGINX Agent v2.41.1 or later. -{{< call-out "note" "Chart renamed in NIM 2.20.0" >}} -The Helm chart has been renamed from `nginx-stable/nms-hybrid` to `nginx-stable/nim`. -Make sure to update your chart references if you’re using version 2.20.0 or later. -{{< /call-out >}} - -{{< call-out "note" "Versioning update from NGINX Instance Manager 2.20.0" >}} -Helm chart versioning was reset with the chart rename in NGINX Instance Manager 2.20.0; `v2.0.0` is the first release under the new nginx-stable/nim chart name. +{{< call-out "note" "Chart renamed with new versioning from NGINX Instance Manager 2.20.0" >}} +Starting with version 2.20.0, the Helm chart was renamed from `nginx-stable/nms-hybrid` to `nginx-stable/nim`. Chart versioning was also reset; `v2.0.0` is the first release under the new name. Be sure to update your chart references if you’re using version `2.20.0` or later. {{< /call-out >}} From 17a9364963574a5f0d0c91d084fa71b8aa599ba5 Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Tue, 1 Jul 2025 14:17:40 +0530 Subject: [PATCH 17/27] Update content/nim/deploy/kubernetes/deploy-using-helm.md Co-authored-by: Travis Martin <33876974+travisamartin@users.noreply.github.com> --- content/nim/deploy/kubernetes/deploy-using-helm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index 46233a780..e64a0e15b 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -181,7 +181,7 @@ utility: tag: ``` -These values are required when pulling images from the NGINX private registry. The chart does not auto-resolve image tags. Update the tag: fields to match the NGINX Instance Manager version you want to install referring the Helm chart table. +These values are required when pulling images from the NGINX private registry. The chart doesn't auto-resolve image tags. Set each `tag:` value to match the NGINX Instance Manager version you want to install. Refer to the Helm chart table for version details. Use the file with the `-f values.yaml` flag when installing the chart. From 8e09029ee6a1fd62ad9773bbc184fb254f44fa63 Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Tue, 1 Jul 2025 14:17:52 +0530 Subject: [PATCH 18/27] Update content/nim/deploy/kubernetes/deploy-using-helm.md Co-authored-by: Travis Martin <33876974+travisamartin@users.noreply.github.com> --- content/nim/deploy/kubernetes/deploy-using-helm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index e64a0e15b..07a5b0646 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -236,7 +236,7 @@ helm status nim -n nim You should see `STATUS: deployed` in the output. -To help you choose the right NGINX Instance Manager chart version, see the following table: +To find the right NGINX Instance Manager chart version, see the following table: {{< include "nim/kubernetes/nms-chart-supported-module-versions.md" >}} From 81d6eb5d862807a726ebf11e380cb9e02987684f Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Tue, 1 Jul 2025 14:19:43 +0530 Subject: [PATCH 19/27] Update content/nim/deploy/kubernetes/deploy-using-helm.md Co-authored-by: Travis Martin <33876974+travisamartin@users.noreply.github.com> --- content/nim/deploy/kubernetes/deploy-using-helm.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index 07a5b0646..bdabb10d3 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -354,14 +354,14 @@ networkPolicies: ### Create a Helm deployment values.yaml file -The `values.yaml` file customizes the Helm chart installation without modifying the chart itself. You can use it to specify image repositories, environment variables, resource requests, and other settings. +The `values.yaml` file customizes the Helm chart installation without changing the chart itself. You can use it to set image repositories, environment variables, resource requests, and other options. -1. Create a `values.yaml` file similar to this example: +1. Create a `values.yaml` file like this example: - - In the `imagePullSecrets` section, add the credentials for your private Docker registry. - - Change the version tag to the version of NGINX Instance Manager you would like to install. Refer Helm chart table for versions. + - In the `imagePullSecrets` section, add your private Docker registry credentials. + - Set the `tag:` field to the version of NGINX Instance Manager you want to install. You can find supported versions in the Helm chart table. - {{< see-also >}} For details on creating a secret, see the Kubernetes [Pull an Image from a Private Registry](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/) documentation. {{}} +For details on creating a secret, see the Kubernetes [Pull an Image from a Private Registry](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/) guide. ```yaml imagePullSecrets: From eeb1ab5318ece9272ffba9defdfc13f120da36b4 Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Tue, 1 Jul 2025 14:19:52 +0530 Subject: [PATCH 20/27] Update content/nim/deploy/kubernetes/deploy-using-helm.md Co-authored-by: Travis Martin <33876974+travisamartin@users.noreply.github.com> --- content/nim/deploy/kubernetes/deploy-using-helm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index bdabb10d3..662e34fb9 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -441,7 +441,7 @@ To upgrade: ``` - Replace `` with the path to the `values.yaml` file you created]({{< ref "/nim/deploy/kubernetes/deploy-using-helm.md#configure-chart" >}}). - - Replace `YourPassword123#` with a secure password that includes uppercase and lowercase letters, numbers, and special characters. + - Replace `` with a secure password that includes uppercase and lowercase letters, numbers, and special characters. {{}} Save this password for future use. Only the encrypted password is stored in Kubernetes, and you can’t recover or reset it later. {{}} From 509d988f57ee0b5f2d5ef9dbdf3745c2e90f5bff Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Tue, 1 Jul 2025 14:31:34 +0530 Subject: [PATCH 21/27] Update content/nim/deploy/kubernetes/deploy-using-helm.md Co-authored-by: Travis Martin <33876974+travisamartin@users.noreply.github.com> --- content/nim/deploy/kubernetes/deploy-using-helm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index 662e34fb9..b2cb583bb 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -405,7 +405,7 @@ For details on creating a secret, see the Kubernetes [Pull an Image from a Priva Run the `helm install` command to deploy NGINX Instance Manager: 1. Replace `` with the path to your `values.yaml` file. -2. Replace `YourPassword123#` with a secure password (containing a mix of uppercase, lowercase letters, numbers, and special characters). +2. Replace `` with a secure password (containing a mix of uppercase, lowercase letters, numbers, and special characters). {{< important >}} Remember to save the password for future use. Only the encrypted password is stored, and there's no way to recover or reset it if lost. {{< /important >}} From fd9a626c3cc2628e3c6f37b574a4cfdd553bfc39 Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Tue, 1 Jul 2025 14:31:44 +0530 Subject: [PATCH 22/27] Update content/nim/deploy/kubernetes/deploy-using-helm.md Co-authored-by: Travis Martin <33876974+travisamartin@users.noreply.github.com> --- content/nim/deploy/kubernetes/deploy-using-helm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index b2cb583bb..ec1028fe7 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -412,7 +412,7 @@ Run the `helm install` command to deploy NGINX Instance Manager: ```shell helm install -n nms-hybrid \ ---set adminPasswordHash=$(openssl passwd -6 'YourPassword123#') \ +--set adminPasswordHash=$(openssl passwd -6 '') \ nms nginx-stable/nms-hybrid \ --create-namespace \ -f \ From 698167c64cb18ca70259ddeb9f7c76eaa8efa5c6 Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Tue, 1 Jul 2025 14:32:17 +0530 Subject: [PATCH 23/27] Update content/nim/deploy/kubernetes/deploy-using-helm.md Co-authored-by: Travis Martin <33876974+travisamartin@users.noreply.github.com> --- content/nim/deploy/kubernetes/deploy-using-helm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index ec1028fe7..bb7d9d996 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -433,7 +433,7 @@ To upgrade: ```shell helm upgrade -n nms \ - --set nms-hybrid.adminPasswordHash=$(openssl passwd -6 'YourPassword123#') \ + --set nms-hybrid.adminPasswordHash=$(openssl passwd -6 '') \ nms nginx-stable/nms-hybrid \ -f \ --version \ From 84c647ba216a26e0c623d3dbe7ea1de2ee2c00ca Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Tue, 1 Jul 2025 14:33:00 +0530 Subject: [PATCH 24/27] Update content/nim/deploy/kubernetes/deploy-using-helm.md Co-authored-by: Travis Martin <33876974+travisamartin@users.noreply.github.com> --- content/nim/deploy/kubernetes/deploy-using-helm.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index bb7d9d996..a677a76ca 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -445,9 +445,11 @@ To upgrade: {{}} Save this password for future use. Only the encrypted password is stored in Kubernetes, and you can’t recover or reset it later. {{}} -{{< call-out "note" "Upgrading from 2.18.0 or lower to 2.19.x" >}} -If you’re upgrading from a deployment that used the legacy `nms` chart or release name, you’ll need to update the chart reference and adjust the release name as needed. -The structure of values.yaml is different from previous releases. +{{< call-out "note" "Upgrading from 2.18.0 or earlier to 2.19.x" >}} +If you're upgrading from version 2.18.0 or earlier to 2.19.x, note the following changes: + +- If you used the legacy `nms` chart or release name, update the chart reference and adjust the release name if needed. +- The structure of the `values.yaml` file has changed in this release. {{< /call-out >}} --- From 97c6ac5a898c52431b77c4eab6cfe464b5e316fa Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Tue, 1 Jul 2025 14:33:43 +0530 Subject: [PATCH 25/27] Update content/nim/deploy/kubernetes/deploy-using-helm.md Co-authored-by: Travis Martin <33876974+travisamartin@users.noreply.github.com> --- content/nim/deploy/kubernetes/deploy-using-helm.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index a677a76ca..ad6b21d4f 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -567,12 +567,13 @@ openshift: This ensures pods can run with the user IDs required by NGINX Instance Manager services. -When `openshift.enabled: true` is set in the `values.yaml` file, the NGINX Instance Manager deployment automatically creates a **custom [Security Context Constraints](https://docs.redhat.com/en/documentation/openshift_container_platform/4.13/html/authentication_and_authorization/managing-pod-security-policies) (SCCs)** and links it to the Service Account used by all pods. +When `openshift.enabled: true` is set in the `values.yaml` file, the NGINX Instance Manager deployment automatically creates a custom [Security Context Constraints (SCC)](https://docs.redhat.com/en/documentation/openshift_container_platform/4.13/html/authentication_and_authorization/managing-pod-security-policies) object and links it to the Service Account used by all pods. -By default, OpenShift enforces strict security policies that require containers to run as **non-root** users. The NGINX Instance Manager deployment needs specific user IDs (UIDs) for certain services, such as **1000** for `nms` and **101** for `nginx` and `clickhouse`. Since the default SCCs do not allow these UIDs, a **custom SCC** is created. This ensures that the deployment can run with the necessary permissions while maintaining OpenShift’s security standards. The custom SCC allows these UIDs by setting the `runAsUser` field, which controls which users can run containers. +By default, OpenShift enforces strict security policies that require containers to run as **non-root** users. The deployment needs specific user IDs (UIDs) for certain services—**1000** for `nms`, and **101** for `nginx` and `clickhouse`. Since the default SCCs don’t allow these UIDs, the deployment creates a custom SCC. This SCC sets the `runAsUser` field to allow the necessary UIDs while still complying with OpenShift’s security standards. -{{< note >}} The NGINX Instance Manager deployment on OpenShift has been tested with OpenShift v4.13.0 Server. {{< /note >}} -{{< note >}} If you see permission errors during deployment, your user account might not have access to manage SCCs. Contact a cluster administrator to request access. {{< /note >}} +This deployment has been tested with OpenShift v4.13.0 Server. + +If you see permission errors during deployment, your account might not have access to manage SCCs. Ask a cluster administrator for access. To verify that the SCC was created after installing the Helm chart, run: From 65fbb1240c6784a7f78932d9aee7d728ebacfb4b Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Tue, 1 Jul 2025 14:49:42 +0530 Subject: [PATCH 26/27] fix: minor yaml fixes --- .../deploy/kubernetes/deploy-using-helm.md | 72 ++++++++++--------- 1 file changed, 40 insertions(+), 32 deletions(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index 827662cd7..e29892e22 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -364,38 +364,46 @@ The `values.yaml` file customizes the Helm chart installation without changing t For details on creating a secret, see the Kubernetes [Pull an Image from a Private Registry](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/) guide. - ```yaml - imagePullSecrets: - - name: regcred - apigw: - image: - repository: private-registry.nginx.com/nms/apigw - tag: - core: - image: - repository: private-registry.nginx.com/nms/core - tag: - dpm: - image: - repository: private-registry.nginx.com/nms/dpm - tag: - ingestion: - image: - repository: private-registry.nginx.com/nms/ingestion - tag: - integrations: - image: - repository: private-registry.nginx.com/nms/integrations - tag: - secmon: - image: - repository: private-registry.nginx.com/nms/secmon - tag: - utility: - image: - repository: private-registry.nginx.com/nms/utility - tag: - ``` +```yaml +imagePullSecrets: + - name: regcred + +apigw: + image: + repository: private-registry.nginx.com/nms/apigw + tag: + +core: + image: + repository: private-registry.nginx.com/nms/core + tag: + +dpm: + image: + repository: private-registry.nginx.com/nms/dpm + tag: + +ingestion: + image: + repository: private-registry.nginx.com/nms/ingestion + tag: + +integrations: + image: + repository: private-registry.nginx.com/nms/integrations + tag: + +secmon: + image: + repository: private-registry.nginx.com/nms/secmon + tag: + +utility: + image: + repository: private-registry.nginx.com/nms/utility + tag: +``` + 2. Save and close the `values.yaml` file. From adabbfabbc7d798aea5cf82001f0d63a6dba4d43 Mon Sep 17 00:00:00 2001 From: Chetan Jain <46200286+Chetan-99@users.noreply.github.com> Date: Tue, 1 Jul 2025 14:56:17 +0530 Subject: [PATCH 27/27] fix: minor changes --- content/nim/deploy/kubernetes/deploy-using-helm.md | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/content/nim/deploy/kubernetes/deploy-using-helm.md b/content/nim/deploy/kubernetes/deploy-using-helm.md index e29892e22..cbf7fa4ef 100644 --- a/content/nim/deploy/kubernetes/deploy-using-helm.md +++ b/content/nim/deploy/kubernetes/deploy-using-helm.md @@ -150,32 +150,26 @@ apigw: image: repository: private-registry.nginx.com/nms/apigw tag: - core: image: repository: private-registry.nginx.com/nms/core tag: - dpm: image: repository: private-registry.nginx.com/nms/dpm tag: - ingestion: image: repository: private-registry.nginx.com/nms/ingestion tag: - integrations: image: repository: private-registry.nginx.com/nms/integrations tag: - secmon: image: repository: private-registry.nginx.com/nms/secmon tag: - utility: image: repository: private-registry.nginx.com/nms/utility @@ -372,32 +366,26 @@ apigw: image: repository: private-registry.nginx.com/nms/apigw tag: - core: image: repository: private-registry.nginx.com/nms/core tag: - dpm: image: repository: private-registry.nginx.com/nms/dpm tag: - ingestion: image: repository: private-registry.nginx.com/nms/ingestion tag: - integrations: image: repository: private-registry.nginx.com/nms/integrations tag: - secmon: image: repository: private-registry.nginx.com/nms/secmon tag: - utility: image: repository: private-registry.nginx.com/nms/utility