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, 15 insertions, 0 deletions

diff --git a/vagrant/tests/vnfs/edgex/kubernetes/services/rulesengine-service.yaml b/vagrant/tests/vnfs/edgex/kubernetes/services/rulesengine-service.yaml
new file mode 100644
index 00000000..238c32ce
--- /dev/null
+++ b/vagrant/tests/vnfs/edgex/kubernetes/services/rulesengine-service.yaml
@@ -0,0 +1,15 @@
+apiVersion: v1
+kind: Service
+metadata:
+  labels:
+    io.kompose.service: edgex-support-rulesengine
+  name: edgex-support-rulesengine
+spec:
+  ports:
+  - name: "48075"
+    port: 48075
+    targetPort: 48075
+  selector:
+    io.kompose.service: edgex-support-rulesengine
+status:
+  loadBalancer: {}