NONRTRIC980: fixs for controlpanel kong, 'hunkey dory' and pms ports

[it/dep.git] / nonrtric / helm / servicemanager / values.yaml

diff --git a/nonrtric/helm/servicemanager/values.yaml b/nonrtric/helm/servicemanager/values.yaml
index dbb261c..0cfaa05 100644 (file)
--- a/nonrtric/helm/servicemanager/values.yaml
+++ b/nonrtric/helm/servicemanager/values.yaml
@@ -38,12 +38,12 @@ data:
   .env: |
     # 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.
+    # From inside the Kong cluster, we can use the Kubernetes cluster DNS entry, oran-nonrtric-kong-proxy.nonrtric.svc.cluster.local.
     KONG_DOMAIN: "kong"
     KONG_PROTOCOL: "http"
-    KONG_CONTROL_PLANE_IPV4: "kong-nonrtric-kong-admin.nonrtric.svc.cluster.local"
+    KONG_CONTROL_PLANE_IPV4: "oran-nonrtric-kong-admin.nonrtric.svc.cluster.local"
     KONG_CONTROL_PLANE_PORT: "8001"
-    KONG_DATA_PLANE_IPV4: "kong-nonrtric-kong-proxy.nonrtric.svc.cluster.local"
+    KONG_DATA_PLANE_IPV4: "oran-nonrtric-kong-proxy.nonrtric.svc.cluster.local"
     KONG_DATA_PLANE_PORT: "80"
     CAPIF_PROTOCOL: "http"
     CAPIF_IPV4: "capifcore.nonrtric.svc.cluster.local"