Internal HTTP Host

By default, HTTP requests submitted by NotifyBC back to itself will be sent to httpHost if defined or the host of the incoming HTTP request that spawns such internal requests. But if config internalHttpHost, which has no default value, is defined, for example in file src/config.local.js

module.exports = {
  internalHttpHost: 'http://notifybc:3000',
};

then the HTTP request will be sent to the configured host. An internal request can be generated, for example, by cron jobs. internalHttpHost shouldn't be accessible from internet.

All internal requests are supposed to be admin requests. The purpose of internalHttpHost is to facilitate identifying the internal server ip as admin ip.

Kubernetes Use Case

The Kubernetes deployment script sets internalHttpHost to notify-bc-app service url in config map. The source ip in such case would be in a private Kubernetes ip range. You should add this private ip range to admin ip list. The private ip range varies from Kubernetes installation. In BCGov's OCP4 cluster, it starts with octet 10.