From 6174db418da20bdab4ee25e38a4470bddb8fc33e Mon Sep 17 00:00:00 2001 From: Lucjan Bryndza Date: Thu, 9 Jul 2020 09:00:20 +0000 Subject: [PATCH] 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 Issue-ID: OOM-2488 --- kubernetes/cds/charts/cds-blueprints-processor/values.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kubernetes/cds/charts/cds-blueprints-processor/values.yaml b/kubernetes/cds/charts/cds-blueprints-processor/values.yaml index 500e3a536b..c481a4b1b3 100755 --- 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" -- 2.16.6