fixing nodeport collisions with sdnc 95/48095/1
authorMandeep Khinda <mandeep.khinda@amdocs.com>
Thu, 17 May 2018 20:16:06 +0000 (20:16 +0000)
committerMandeep Khinda <mandeep.khinda@amdocs.com>
Thu, 17 May 2018 20:16:06 +0000 (20:16 +0000)
I am told that the sdnc geo feature needs a well known
set of node ports and they have selected a contigous block
so I am changing the other charts

Issue-ID: OOM-1096

Change-Id: I237d126e96174726902422bf842135304764c7d2
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
kubernetes/cli/values.yaml
kubernetes/nbi/values.yaml

index dd034f7..bd52ced 100644 (file)
@@ -59,7 +59,7 @@ service:
   internalPort: "80"
   internalPort1: 8080
   nodePort: "60"
-  nodePort1: "61"
+  nodePort1: "71"
 
 ingress:
   enabled: false
index 5557edf..709e580 100644 (file)
@@ -97,7 +97,7 @@ service:
   type: NodePort
   portName: api
   name: nbi
-  nodePort: 64
+  nodePort: 74
   internalPort: 8080
 
 ingress: