X-Git-Url: https://gerrit.o-ran-sc.org/r/gitweb?a=blobdiff_plain;f=smo-install%2Foran_oom%2Fservicemanager%2Fvalues.yaml;h=fb536718a114d23a1297a4d892aa1344419d4959;hb=1fd14f960d45794d4b87135ba2e2e72244987f03;hp=a0a4ffda87ef6c771017871b589d77f0b490cdb5;hpb=d477ffdd450fa71dc8e8705f859b8520a59b1803;p=it%2Fdep.git

diff --git a/smo-install/oran_oom/servicemanager/values.yaml b/smo-install/oran_oom/servicemanager/values.yaml
index a0a4ffda..fb536718 100644
--- a/smo-install/oran_oom/servicemanager/values.yaml
+++ b/smo-install/oran_oom/servicemanager/values.yaml
@@ -61,7 +61,7 @@ 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: "oran-nonrtric-kong-admin.nonrtric.svc.cluster.local"