Deploy NBS Gateway for NBS 7

This page walks through deploying the NBS Gateway using the nbs-gateway Helm chart from the NEDSS-Helm repository for NBS version 7.13. NBS Gateway routes requests between NBS 7 microservices and the legacy NBS 6 application.

Prerequisites

This page assumes you’ve completed Before you begin for the microservices phase and each microservice deployment page before this one, in order. The page immediately before this one is Validate Elasticsearch, Modernization API, and NiFi.

Have your domain values and Keycloak client secret available. See the Helm values reference and Import service clients and retrieve secrets if you need help determining any values.

Deploy NBS Gateway using Helm

Complete the following steps to deploy the ‘nbs-gateway’ Helm chart from the charts/nbs-gateway/ directory of your cloned NEDSS-Helm repository:

Search values.yaml for EXAMPLE and fill in your environment-specific values:
- For the NBS 7 and NBS 6 application domain values, use the DNS records table.
- For the OIDC client secret used for Keycloak login authentication, see Import service clients and retrieve secrets.
Confirm the following feature flags in values.yaml:
- Page Builder is disabled:
```
pageBuilder:
  enabled: "false"
```
- OIDC is enabled:
```
oidc:
  enabled: "true"
  client:
    id: "nbs-modernization"
```
- Report execution is enabled. For report execution to work, this flag must also be "true" in the Modernization API deployment:
```
 reportExecution:
   enabled: "true"
```

Install NBS Gateway:

helm install "nbs-gateway" ./nbs-gateway -f ./nbs-gateway/values.yaml

Confirm the pod is running before proceeding to the next deployment:
```
kubectl get pods
```

If the pod is not in a running state, wait and troubleshoot before continuing.

Next steps

Continue to Data processing.