X-Git-Url: https://gerrit.o-ran-sc.org/r/gitweb?a=blobdiff_plain;f=nonrtric%2Fhelm%2Fservicemanager%2Fvalues.yaml;fp=nonrtric%2Fhelm%2Fservicemanager%2Fvalues.yaml;h=0cfaa055036222eafa649da8a21e4e0f2c336ac3;hb=1fd14f960d45794d4b87135ba2e2e72244987f03;hp=dbb261c74b5fe64ca64864a3158b4dc82bf00ab6;hpb=d477ffdd450fa71dc8e8705f859b8520a59b1803;p=it%2Fdep.git

diff --git a/nonrtric/helm/servicemanager/values.yaml b/nonrtric/helm/servicemanager/values.yaml
index dbb261c7..0cfaa055 100644
--- 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"