[DCAEGEN2] Update cm-container and consul-loader

cm-container 4.2.0 fixes a restart issue
consul-loader-container 1.1.0 adds functionality
needed for deploying DCAE microservices with Helm

Issue-ID: DCAEGEN2-2581
Issue-ID: DCAEGEN2-2616
Signed-off-by: Jack Lucas <jflos@sonoris.net>
Change-Id: I3999767d51ce7135c2783a7eee6dadd0b3270d4f
diff --git a/kubernetes/dcaegen2/components/dcae-cloudify-manager/values.yaml b/kubernetes/dcaegen2/components/dcae-cloudify-manager/values.yaml
index 891c0e1..711c1d5 100644
--- a/kubernetes/dcaegen2/components/dcae-cloudify-manager/values.yaml
+++ b/kubernetes/dcaegen2/components/dcae-cloudify-manager/values.yaml
@@ -24,7 +24,7 @@
   nodePortPrefix: 302
   persistence: {}
   tlsImage: onap/org.onap.dcaegen2.deployments.tls-init-container:2.1.0
-  consulLoaderImage: onap/org.onap.dcaegen2.deployments.consul-loader-container:1.0.0
+  consulLoaderImage: onap/org.onap.dcaegen2.deployments.consul-loader-container:1.1.0
   repositoryCred:
     user: docker
     password: docker
@@ -50,7 +50,7 @@
 # Application configuration defaults.
 #################################################################
 # application image
-image: onap/org.onap.dcaegen2.deployments.cm-container:4.1.0
+image: onap/org.onap.dcaegen2.deployments.cm-container:4.2.0
 pullPolicy: Always
 
 # name of shared ConfigMap with kubeconfig for multiple clusters