...
When Service Manager starts, it reads a .env file where you can configure information such as the Kong control and data planes' host and port, the CAPIF host and port, and the Service Manager port.
Sample .env
Code Block | ||
---|---|---|
| ||
KONG_DOMAIN=<string> KONG_PROTOCOL=<http or https protocol scheme> KONG_IPV4=<host string> KONG_DATA_PLANE_PORT=<port number> KONG_CONTROL_PLANE_PORT=<port number> CAPIF_PROTOCOL=<http or https protocol scheme> CAPIF_IPV4=<host> CAPIF_PORT=<port number> LOG_LEVEL=<Trace, Debug, Info, Warning, Error, Fatal or Panic> SERVICE_MANAGER_PORT=<port number> TEST_SERVICE_IPV4=<host string> TEST_SERVICE_PORT=<port number> |
...
nonrtric:
installPms: false
installA1controller: false
installA1simulator: false
installControlpanel: false
installInformationservice: false
installRappcatalogueservice: false
installRappcatalogueenhancedservice: false
installNonrtricgateway: false
installKong: true
installDmaapadapterservice: false
installDmaapmediatorservice: false
installHelmmanager: false
installOrufhrecovery: false
installRansliceassurance: false
installCapifcore: true
installServicemanager: true
installRanpm: false
# rApp Manager functionality relies on ACM for its operation
installrAppmanager: false
# DME Participant should only be activated when ACM installation is available for this participant to utilize
installDmeParticipant: false
.env
The .env file is volume mounted into the Docker container from a config map as container run-time.
Kong Clean Up
Please note that when doing an undeployment, we remove any Kong services and routes that are flagged with each of the following tags.
...