Fix configuration for ingress CDS blueprints

Fix wrong configuration for ingress CDS
blueprints processor, causes that the service
is inaccessible trough ingress controller

Change-Id: I3ecd0ec6f5dd882be615bd1a5f617781ae4d486b
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
Issue-ID: OOM-2488

diff --git a/kubernetes/cds/charts/cds-blueprints-processor/values.yaml b/kubernetes/cds/charts/cds-blueprints-processor/values.yaml
index 500e3a5..c481a4b 100755 (executable)
--- a/kubernetes/cds/charts/cds-blueprints-processor/values.yaml
+++ b/kubernetes/cds/charts/cds-blueprints-processor/values.yaml
@@ -154,7 +154,7 @@ ingress:
   enabled: false
   service:
     - baseaddr: "blueprintsprocessorhttp"
-      name: "blueprints-processor-http"
+      name: "cds-blueprints-processor-http"
       port: 8080
   config:
     ssl: "none"