From 87f249320b8bf55a4037a75f16170b287e3b6ee6 Mon Sep 17 00:00:00 2001 From: Kiran Kamineni Date: Thu, 11 Oct 2018 03:13:15 -0700 Subject: 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 --- .../kubernetes/services/device-bluetooth-service.yaml | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 vagrant/tests/vnfs/edgex/kubernetes/services/device-bluetooth-service.yaml (limited to 'vagrant/tests/vnfs/edgex/kubernetes/services/device-bluetooth-service.yaml') diff --git a/vagrant/tests/vnfs/edgex/kubernetes/services/device-bluetooth-service.yaml b/vagrant/tests/vnfs/edgex/kubernetes/services/device-bluetooth-service.yaml new file mode 100644 index 00000000..48ffc9ef --- /dev/null +++ b/vagrant/tests/vnfs/edgex/kubernetes/services/device-bluetooth-service.yaml @@ -0,0 +1,15 @@ +apiVersion: v1 +kind: Service +metadata: + labels: + io.kompose.service: edgex-device-bluetooth + name: edgex-device-bluetooth +spec: + ports: + - name: "49988" + port: 49988 + targetPort: 49988 + selector: + io.kompose.service: edgex-device-bluetooth +status: + loadBalancer: {} -- cgit 1.2.3-korg