WatchTower alert-insights-api pod fails to start "apiml.service.ssl.keyStore property not configured"

Products

• WatchTower

Issue/Introduction

When deploying the WatchTower alert-insights capability in a Kubernetes environment the alert-insights-api pod fails to start. Error messages issued:

ERROR org.springframework.boot.SpringApplication - Application run failed
java.lang.IllegalArgumentException: apiml.service.ssl.keyStore property not configured
ERROR com.broadcom.restapi.sdk.lifecycle.LifeCycleLogger - BRSA112E Alert Insights server startup failed

 

 

Environment

WatchTower 1.3

Cause

The alert-insights-api service requires the environment variable, apiml_service_ssl_keyStore, to be defined in its deployment manifest.

This property tells the application where to locate the SSL keystore file required for secure communication (APIML integration).  Failure to define this property in the container's environment causes the Spring Boot context initialization to fail.

Resolution

Manually add apiml_service_ssl_keyStore to the alert-insights-api deployment YAML as below:

1. Locate and edit 'alert-insights-api' yaml.
   
   
2. Add the parameter and value below:
   
   - name: apiml_service_ssl_keyStore
          value: /etc/opt/brcm/AlertInsights/certs/key-store

   #Note /etc/opt/brcm/AlertInsights/certs/key-store is a default, specific volume mount path should be verified


3. Save yaml file and apply the changes as below
   
   kubectl apply -f alert-insights-api.yaml


4. Monitor pod logs for successful startup - 'BRSA110I Alert Insights server startup initiated'.