Merge "NONRTRIC-946: Servicemanager - add Kong data plane and control plane"

[nonrtric/plt/sme.git] / servicemanager / .env.example

diff --git a/servicemanager/.env.example b/servicemanager/.env.example
index 5f7bfe1..1d3c4ef 100644 (file)
--- a/servicemanager/.env.example
+++ b/servicemanager/.env.example
@@ -1,12 +1,16 @@
+# The Kong Data plane provides the endpoint that Service Manager gives to the rApp so that the rApp can invoke the CAPIF published API.
+# In a Kubernetes environment, we need to use the Kong NodePort IP and nodePort if the rApp needs access from outside the Kong cluster.
+# From inside the Kong cluster, we can use the Kubernetes cluster DNS entry, kong-nonrtric-kong-proxy.nonrtric.svc.cluster.local.
 KONG_DOMAIN=<string>
 KONG_PROTOCOL=<http or https protocol scheme>
-KONG_IPV4=<host string>
-KONG_DATA_PLANE_PORT=<port number>
+KONG_CONTROL_PLANE_IPV4=<host string>
 KONG_CONTROL_PLANE_PORT=<port number>
+KONG_DATA_PLANE_IPV4=<host string>
+KONG_DATA_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>
\ No newline at end of file
+TEST_SERVICE_PORT=<port number>