Table of contents

  1. Deploy Data Sync Service API via helm chart
    1. Data Sync Microservice

Deploy Data Sync Service API via helm chart

This guide sets out the detailed steps to install NBS 7 Data Sync service that will be used to extract the data for NNDSS and STLT Reporting needs. The Data Sync service provides a secure API to connect to the databases in the NBS cloud, with an API endpoint service and without interrupting any operations On-Prem at Jurisdictions.

Data Sync Microservice

  1. Please use the values file supplied as part of [nbs-helm-.zip](https://github.com/CDCgov/nbs-helm/releases). Use this [link](https://github.com/CDCgov/nbs-helm/releases) to download the zip file (scroll down to the Assets listed for the latest or previous releases). The `values.yaml` file should be under `charts\nnd-service\values.yaml`. Values for *ECR repository, ECR image tag, db server endpoints, and ingress host* should be provided in the `values.yaml` file.

  2. Confirm that the following DNS entry were created and pointed to the network load balancer in front of your Kubernetes cluster (make sure this is the ACTIVE NLB provisioned via nginx-ingress in the base install steps). This should be done in your authoritative DNS service (e.g., Route 53).
    Please replace http://example.com with the appropriate domain name in the values.yaml file.
    NND service Application – e.g. data.example.com

  3. Update the image repository and tag with the following:

    image:
  repository: "quay.io/us-cdcgov/cdc-nbs-modernization/nnd-service"
  pullPolicy: IfNotPresent
  tag: <release-version-tag> e.g v1.0.1

  4. Update the values file with the jdbc connection values in the following format. The dbserver value is just a database server endpoint. Please don’t include the port number. nnd-dbendpoint

    jdbc:
  dbserver: "cdc-nbs-xxxxxxxxxxxx.us-east-1.rds.amazonaws.com"
  username: "DBUsername"
  password: "DBPassword"

  5. Update the values.yaml to populate efsFileSystemId which is the EFS file system id from the AWS console. See image below. nnd-efs

    efsFileSystemId: "EXAMPLE_EFS_ID"
  6. Keycloak Auth URI. Provide keycloak auth uri in the values.yaml file as shown below. In the default configuration this value should not need to change unless the name or namespace of the keycloak pod is modified. 
    authUri: "http://keycloak.default.svc.cluster.local/auth/realms/NBS"
  7. Run the following command to install nnd-service. 
    helm install nnd-service -f ./nnd-service/values.yaml nnd-service
    • Note: Check to see if the pod for nnd-service is running using kubectl get pods

Table of contents