Fix ncm port in Helm Chart

Issue-ID: MULTICLOUD-1065
Signed-off-by: Ritu Sood <ritu.sood@intel.com>
Change-Id: I45dfca5007e030420da9228ff698bfb729348dd4

diff --git a/deployments/helm/v2/onap4k8s/ncm/resources/config/config.json b/deployments/helm/v2/onap4k8s/ncm/resources/config/config.json
index 81728ea..f1fad4b 100644 (file)
--- a/deployments/helm/v2/onap4k8s/ncm/resources/config/config.json
+++ b/deployments/helm/v2/onap4k8s/ncm/resources/config/config.json
@@ -3,5 +3,6 @@
     "database-type": "mongo",
     "database-ip": "emco-mongo",
     "etcd-ip": "emco-etcd",
-    "service-port": "9016"
-}
\ No newline at end of file
+    "service-port": "9031"
+}
+

diff --git a/deployments/helm/v2/onap4k8s/ncm/values.yaml b/deployments/helm/v2/onap4k8s/ncm/values.yaml
index e495cd6..afd3f3f 100644 (file)
--- a/deployments/helm/v2/onap4k8s/ncm/values.yaml
+++ b/deployments/helm/v2/onap4k8s/ncm/values.yaml
@@ -54,7 +54,7 @@ readiness:
   periodSeconds: 30
 
 service:
-  type: ClusterIP
+  type: NodePort
   name: ncm
   portName: ncm
   internalPort: 9031