Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2019-03-08 | Add test helm chart for testing | 13 | -0/+473 | ||
Add a test helm chart for testing the end to end flow. This chart brings up a service and a deployment. The deployment brings up two containers, vault and consul. Vault and Consul are brought up in dev mode. The helm chart also has a subchart, common, which contains templates that are used within the main chart. Added an override deployment.yaml which creates only one container instead of two Fixed plugin.sh and tar file creation steps Issue-ID: MULTICLOUD-291 Change-Id: I7eb10c9f43f8a4e09938139b5e2edee5d59feb3b Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com> Signed-off-by: Victor Morales <victor.morales@intel.com> | |||||
2018-10-18 | Add edgex yaml to helm based template | 57 | -0/+2118 | ||
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> |