aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/dmaap/templates/configmap.yaml
AgeCommit message (Collapse)AuthorFilesLines
2020-10-21[DMAAP] change comment styleJakub Latusek1-0/+2
Signed-off-by: Jakub Latusek <j.latusek@samsung.com> Change-Id: I1f0fa48fe6dbca7fa319d5b60ac7d1ffb8def194 Issue-ID: OOM-2562
2020-02-01[ONAP-wide] Replace .Release.Name with common.releaseKrzysztof Opasiak1-1/+1
ONAP is too big to be deployed using helm install so we need to use a custom helm plugin helm deploy. This script deloys onap component by component instead of deploying evrything at once. Unfortunately this script also modifies the helm release by appending component name to it. As a result of this behavior our objects are called for example: onap-mariadb-galera-mariadb-galera-0 instead of just being called onap-mariadb-galera-0. This patch simplifies this naming convention by replacing all direct usages of .Release.Name with common.release macro which strips the component specific part from the release name. Issue-ID: OOM-2275 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: Ia8cead50d305adb00eef666d0a1ace74479b5183
2019-03-14Attempt2: Post-install jobs for DMaaP ProvisioningdglFromAtt1-1/+1
This was originally committed under 81992 but got a merge conflict. I messed up resolving it so I abandoned 81992 and created this new commit. patchset2: replaced Release.Name for common.fullname in one of the charts patchset3: at Borislav's request, changed other references to common.fullname so the approach is consistent throughout the configmaps used for initialization. Along the way, hit a limit of 53 chars on some resource name. So changed the directory from the verbose dmaap-bus-controller to the more terse dbc. Change-Id: I1078003de094fee95c681f7fdaecb567235b7b3e Signed-off-by: dglFromAtt <dgl@research.att.com> Issue-ID: DMAAP-904 Signed-off-by: dglFromAtt <dgl@research.att.com>
2019-02-21Add filebeat sidecar container for dmaap-dreconwar1-0/+26
Change-Id: I3f81a683832ec37598e165c859944ab97a9ffc51 Issue-ID: DMAAP-853 Signed-off-by: econwar <conor.ward@est.tech>
2018-04-30Integration w common/postgresDominic Lunanuova1-21/+0
Patchset 1: first cut at integration with common/postgres Patchset 2: Mandeep Khinda - refactored charts to standardize Wired in shared postgres chart Patchset 6: Introduced simple dmaap/Makefile to force helm dep up in the deeper charts directory. Includes slight modification to parent make clean target Patchset 8: merge conflict again Change-Id: If59f08638bac8761ae5452b60f172c99fcf4ec86 Signed-off-by: Dominic Lunanuova <dgl@research.att.com> Issue-ID: DMAAP-117 Signed-off-by: Dominic Lunanuova <dgl@research.att.com>
2018-04-04Initial chart for dmaap - 2nd attemptDominic Lunanuova1-0/+21
This should conform to new OOM standard helm structure. It starts a directory called dmaap which will hold all dmaap components. But for now it only has buscontroller. Once we get this working, we can add message-router. (see DMAAP-386) Patch 2 gets private postgresql working. I'd prefer to integreate with common postgresql from Tony in a future commit to avoid any immediate delivery timing dependency. Patch 3 corrects some port mapping from service to pod. Change-Id: Id9838d7ddb2ccccfc8b0e3f3b9e50f9b5672c484 Signed-off-by: Dominic Lunanuova <dgl@research.att.com> Issue-ID: DMAAP-117 Signed-off-by: Dominic Lunanuova <dgl@research.att.com>