[MULTICLOUD] Service mesh compatibility

Patch on MC charts dedicated to make http/https calls depending
on configuration for TLS. Include an updated version of the
framework-artifactbroker

Issue-ID: OOM-3015

Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
Change-Id: I03deae9dcea703540fe6e3a81ddba20505f246f1
diff --git a/kubernetes/multicloud/components/multicloud-vio/values.yaml b/kubernetes/multicloud/components/multicloud-vio/values.yaml
index 17643ba..3b852df 100644
--- a/kubernetes/multicloud/components/multicloud-vio/values.yaml
+++ b/kubernetes/multicloud/components/multicloud-vio/values.yaml
@@ -23,7 +23,7 @@
 # Application configuration defaults.
 #################################################################
 # application image
-image: onap/multicloud/vio:1.4.1
+image: onap/multicloud/vio:1.4.2
 pullPolicy: Always
 
 #Istio sidecar injection policy
@@ -32,9 +32,11 @@
 # application configuration
 config:
   msbgateway: msb-iag
-  msbPort: 80
+  msbPort: 443
+  msbPlainPort: 80
   aai:
-    port: 8443
+    aaiPort: 8443
+    aaiPlainPort: 8080
     schemaVersion: v13
     username: AAI
     password: AAI
@@ -58,7 +60,7 @@
 service:
   type: ClusterIP
   name: multicloud-vio
-  portName: multicloud-vio
+  portName: http
   externalPort: 9004
   internalPort: 9004
   nodePort: 92