Deploy the Case Notification service for NBS 7

This page walks through deploying the Case Notification service using the case-notification-service Helm chart from the NEDSS-Helm repository for NBS version 7.13.

On this page

  1. Prerequisites
  2. Deploy the Case Notification service using Helm
  3. Validate the deployment
  4. Next steps

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 Debezium Kafka connector deployment for case notifications.

Deploy the Case Notification service using Helm

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

  1. In the case-notification-service/values.yaml file, search for EXAMPLE and fill in your environment-specific values for the ingress host, JDBC connection, and Kafka cluster endpoint. The dbserver value is the database server endpoint only; do not include the port number. The Helm values reference lists the values to use. For a full list of environment variables, see the NEDSS-NNDSS-Case-Notifications README and the case-notification-service deployment template.

  2. Install the Case Notification service:

    helm install "case-notification-service" ./case-notification-service -f ./case-notification-service/values.yaml

  3. Confirm the pod is running before continuing:

    kubectl get pods

Validate the deployment

Use the actuator endpoints to confirm the service is running.

Run the info endpoint to confirm the service version and build details:

https://<data.EXAMPLE_DOMAIN>/case-notification/actuator/info

Run the health endpoint to confirm the service is running:

https://<data.EXAMPLE_DOMAIN>/case-notification/actuator/health

Next steps

After confirming a successful deployment, continue to API testing to test and integrate the case notification APIs.