summaryrefslogtreecommitdiffstats
path: root/kubernetes/dcaegen2-services/components/dcae-tcagen2/templates
AgeCommit message (Collapse)AuthorFilesLines
2022-03-23[DCAEGEN2] Remove Consul loader init containerJack Lucas1-19/+0
DCAE microservices no longer rely on Consul to store their configuration information. This change modifies the common DCAE microservice deployment template to eliminate the initContainer that loads configuration information into Consul. Issue-ID: DCAEGEN2-3059 Signed-off-by: Jack Lucas <jflos@sonoris.net> Change-Id: I4d9d547de020fe1987afab1c99cd033799ed7b36
2021-09-03[DCAEGEN2] Add Consul key delete jobJack Lucas1-0/+19
Add a job for each microservice that deletes the Consul key holding the microservice's configuration when the microservice is undeployed. (Fixes a bug in an earlier version that would loop indefinitely if Consul had been undeployed first.) Issue-ID: DCAEGEN2-2669 Signed-off-by: Jack Lucas <jflos@sonoris.net> Change-Id: I9172fc014b79d2cc07c0b1a1a187a28c63b1838a
2021-03-21[DCAEGEN2] Deploy DCAE microservices via HelmJack Lucas4-0/+76
Deploy DCAE microservices using Helm instead of having the DCAE bootstrap container deploy them using Cloudify. Charts for the microservices are found under oom/kubernetes/dcaegen2-services. Issue-ID: DCAEGEN2-2615 Issue-ID: DCAEGEN2-2617 Signed-off-by: Jack Lucas <jflos@sonoris.net> Change-Id: I22d88987ae8e21b3c08f31f13ffda98967d13297 [Use common secret template for secrets] Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>