Add edgex yaml to helm based template

Add existing deployment and service yaml files into
a helm chart that can reused.
Currently splitting out consul and mongo as subcharts while
keeping the rest under the main edgex chart.
P2: Convert to different label selectors
P3: Keep the old configuration yaml in a seperate kubernetes folder
P4: Removed common chart with the templates. We are using only a small subset
    which we can expand locally via Helm Variables

Issue-ID: MULTICLOUD-376
Change-Id: I8e0682c7d1d2433b9754209b2f3eedb790df5464
Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>

1 files changed, 0 insertions, 46 deletions

diff --git a/vagrant/tests/edgex/deployments/mongo-deployment.yaml b/vagrant/tests/edgex/deployments/mongo-deployment.yaml
deleted file mode 100644
index 26df5f02..00000000
--- a/vagrant/tests/edgex/deployments/mongo-deployment.yaml
+++ /dev/null
@@ -1,46 +0,0 @@
-apiVersion: apps/v1
-kind: Deployment
-metadata:
-  labels:
-    io.kompose.service: edgex-mongo
-  name: edgex-mongo
-spec:
-  selector:
-      matchLabels:
-        io.kompose.service: edgex-mongo
-  replicas: 1
-  template:
-    metadata:
-      labels:
-        io.kompose.service: edgex-mongo
-    spec:
-      containers:
-      - image: edgexfoundry/docker-edgex-mongo:0.2
-        name: edgex-mongo
-        ports:
-        - containerPort: 27017
-        resources: {}
-        volumeMounts:
-        - mountPath: /data/db
-          name: data-db
-        - mountPath: /edgex/logs
-          name: edgex-logs
-        - mountPath: /consul/config
-          name: consul-config
-        - mountPath: /consul/data
-          name: consul-data
-      restartPolicy: Always
-      volumes:
-      - name: data-db
-        hostPath:
-          path: /data/db
-      - name: edgex-logs
-        hostPath:
-          path: /edgex/logs
-      - name: consul-config
-        hostPath:
-          path: /consul/config
-      - name: consul-data
-        hostPath:
-          path: /consul/data
-status: {}