summaryrefslogtreecommitdiffstats
path: root/kubernetes/dcaegen2/components
AgeCommit message (Collapse)AuthorFilesLines
2020-02-12Pick up new tls init containerJack Lucas16-50/+32
Remove unneeded dashboard inputs file Prepend release name to filebeat configmap name Issue-ID: DCAEGEN2-917 Issue-ID: DCAEGEN2-1923 Issue-ID: DCAEGEN2-1805 Signed-off-by: Jack Lucas <jflucas@research.att.com> Change-Id: I53ef20046d7e16c4e0a2defd41c846d91af4ec09
2020-02-07[COMMON] Remove pgpoolKrzysztof Opasiak1-12/+0
It seems that pgpool is never thus there is no need to spend time moving it to common secret template Issue-ID: OOM-2250 Change-Id: I237f9e01cec80bd47ff47c7eb4db282471cfad07 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
2020-02-02Merge "Update PRH version to 1.5.0"Borislav Glozman1-1/+1
2020-02-02Merge "redis config optimization"Borislav Glozman1-4/+2
2020-02-02Merge "Update ves collector image"Borislav Glozman1-1/+1
2020-02-01[ONAP-wide] Replace .Release.Name with common.releaseKrzysztof Opasiak28-52/+52
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
2020-01-29Update PRH version to 1.5.0pwielebs1-1/+1
Issue-ID: OOM-2281 Signed-off-by: Piotr Wielebski <piotr.wielebski@nokia.com> Change-Id: I0330b2c239af12f48202062954a623c18ca1ac7f
2020-01-28Update ves collector imagePawel1-1/+1
Issue-ID: OOM-2280 Signed-off-by: Pawel <pawel.kasperkiewicz@nokia.com> Change-Id: Iaa80eb212ba0c31ffdceb79e776cd92d38b304d6
2020-01-21redis config optimizationVijay Venkatesh Kumar1-4/+2
- replication count set to 3 - removing nodeport Change-Id: Ie3431c59ffdd44f207eddfbc013ab4fc3f6ed5f9 Signed-off-by: Vijay Venkatesh Kumar <vv770d@att.com> Issue-ID: DCAEGEN2-1720 Issue-ID: OJSI-187
2019-12-17[COMMON] Use deployment for postgresqlSylvain Desbureaux2-2/+4
Instead of statefulset + inner work in the container, use deployments in order to be more reliable Change-Id: Icf4fe1303ae3489c822558e28bb08b69af2d4970 Issue-ID: OOM-2234 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2019-12-11Merge "[DCAE] Use global storage templates for PVC"Borislav Glozman6-215/+46
2019-12-06Merge "Update prh to 1.3.2"Sylvain Desbureaux1-1/+1
2019-12-06Add ingress controler support to DCAELucjan Bryndza2-1/+10
Issue-ID: OOM-2178 Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com> Change-Id: Id4c679431d5d5e0362acbd08757250f1bb5a0616 Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
2019-12-06Update prh to 1.3.2Joanna Jeremicz1-1/+1
Issue-ID: INT-1181 Signed-off-by: Joanna Jeremicz <joanna.jeremicz@nokia.com> Change-Id: I13888ca2334cfb1f59bbcf195726996cd8a79e54
2019-12-04[DCAE] Use global storage templates for PVCSylvain Desbureaux6-215/+46
OOM has now templates in order to create the needed PVC, using: * a PV with a specific class when using a common nfs mount path between nodes (sames as today use) --> is the default behavior today * or a storage class if we want to use dynamic PV. On this case, we use (in order of priority): - persistence.storageClassOverride if set on the chart - global.persistence.storageClass if set globally - persistence.storageClass if set on the chart I've also used a "range" for PV creation of redis in order to have only the needed number. Change-Id: I6bb326f8aaece11bcf503e9300e5c39a87214f81 Issue-ID: OOM-1227 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2019-11-07Attempt 2 at chart restructureUbuntu96-0/+5029
Helm value override file now supports component-specific settings: dcae-bootstrap: enabled: true dcae-cloudify-manager: enabled: true dcae-config-binding-service: enabled: true dcae-healthcheck: enabled: true dcae-redis: enabled: true dcae-servicechange-handler: enabled: true dcae-inventory-api: enabled: true dcae-deployment-handler: enabled: true dcae-policy-handler: enabled: true dcae-dashboard: enabled: true Issue-ID: OOM-1574 Signed-off-by: Ubuntu <dgl@research.att.com> Change-Id: I85e0fe6ae19e176d954611549ec954a5fe662307 Signed-off-by: Ubuntu <dgl@research.att.com>