aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/clamp/charts
AgeCommit message (Collapse)AuthorFilesLines
2020-07-14Make CLAMP compatible with Kubernetes v1.17Magdalena_Biernacka5-5/+20
Issue-ID: OOM-2449 Signed-off-by: Magdalena Biernacka <magdalena.1.biernacka@nokia.com> Change-Id: I75090aac67139465bb5f4030129361ea771c11d2
2020-07-06Release Clamp 5.0.7sebdet1-1/+1
Release clamp 5.0.7 containing an important fix for clamp-857 Issue-ID: CLAMP-857 Signed-off-by: sebdet <sebastien.determe@intl.att.com> Change-Id: I94b0d11ca0e6fdf441784c8cb77860d002923dad (cherry picked from commit f80ad5609f2e271eaa9d3c9c693f5d5c289c250e)
2020-05-25[CLAMP] Allow to use ' in clamp mariadb passwordsKrzysztof Opasiak3-0/+213
' is one of characters that are placed in passwords by our default password generation algorith. As ' is a special character in SQL files we need to escape it before substituting environment variables in .sql file. Issue-ID: OOM-2317 Reported-by: Fiachra Corcoran <fiachra.corcoran@est.tech> Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: I0423b0eaecf7cc16892c10b14881c4d09a24a1d0
2020-05-05Merge "[CLAMP] Configure Ingress for Kibana"Krzysztof Opasiak2-0/+21
2020-05-05[CLAMP] Configure Ingress for KibanaSylvain Desbureaux2-0/+21
Clamp Kibana didn't had a proper ingress, adding it. Issue-ID: OOM-2175 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: I584bffc776789e7e527ffe24fb6ea73f42aebd59
2020-05-04remove hardcoded MariaDB passwordJulienBe10-92/+69
This aligns with other changes on OOM. You can either supply a specific password or have it generated for you based on a master password Issue-ID: CLAMP-796, OJSI-188 Change-Id: If1b80fc47cf1033e094f8a106746d1e8c556c08b Signed-off-by: JulienBe <jb379x@att.com> Co-authored-by: sebdet <sebastien.determe@intl.att.com> [small updates in common secret template usage] Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
2020-04-27Merge "[CLAMP] use common templates for logs"Krzysztof Opasiak6-39/+19
2020-04-22[CLAMP] use common templates for logsSylvain Desbureaux6-39/+19
Using the common templates for centralized logging. Issue-ID: OOM-2370 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: I4824e11bd2be971d15e3a39510f544d2c36b05fd
2020-04-20Release Clamp 5.0.4sebdet1-1/+1
Release clamp 5.0.4 containing all the fixes from CLAMP-R6 Sprint 5 Issue-ID: CLAMP-822 Signed-off-by: sebdet <sebastien.determe@intl.att.com> Change-Id: I02cf0de0569f236f56be482a301ef61121c89ffb
2020-04-03Bump up clamp to 5.0.3sebdet1-1/+1
Due to some fixes for policy communication, we have to bump up clamp to 5.0.3 Issue-ID: CLAMP-819 Signed-off-by: sebdet <sebastien.determe@intl.att.com> Change-Id: I46eed4fa23e92002a6b80f4d1b00e5ba27b4edd2
2020-04-02Merge "Bump chart version"Morgan Richomme9-9/+9
2020-04-02Bump chart versionSylvain Desbureaux9-9/+9
Use 6.0.0 in preparation for Frankfurt release Issue-ID: OOM-2320 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: I8ad82dfdf48b56c38c0e85d640b18cc13c8d9e67
2020-04-02Remove logback and bump up the clamp versionsebdet3-326/+2
Remove the logback file not used anymore and bump up clamp version Issue-ID: CLAMP-812 Signed-off-by: sebdet <sebastien.determe@intl.att.com> Change-Id: Ic3576039df21eb8aa27064188c56c0117aea1ceb
2020-03-31Merge "Update CLAMP deployment for Frankfurt release (RC0)"Sylvain Desbureaux4-54/+211
2020-03-30Update CLAMP deployment for Frankfurt release (RC0)sebdet4-54/+211
Update the SQL and settings of Clamp + set the docker image to current release Issue-ID: CLAMP-795 Signed-off-by: sebdet <sebastien.determe@intl.att.com> Change-Id: Idaa4935516237221c90c4cf9141136fa1e104a02
2020-03-03ES non-rootosgn422w3-3/+3
ElasticSearch run as non-root user Issue-ID: CLAMP-668 Change-Id: I786e2ff8babf4b78fa6dfdf63ff9cd486099fbac Signed-off-by: osgn422w <gervais-martial.ngueko@intl.att.com>
2020-02-21move to OpenDistroosgn422w14-317/+108
move dashboard to Opendistro and certificate update Issue-ID: CLAMP-483 Change-Id: Ibaba1d517c13adeab611ab23749fb16295081372 Signed-off-by: osgn422w <gervais-martial.ngueko@intl.att.com>
2020-02-01[ONAP-wide] Replace .Release.Name with common.releaseKrzysztof Opasiak20-41/+41
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-12-06[CLAMP] Use global storage templates for PVCSylvain Desbureaux4-15/+10
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 Change-Id: I2cc90fe7a22a04d47d406b854c3a75502e539a25 Issue-ID: OOM-1227 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2019-11-05[CLAMP] set Mariadb PVC to RWOSylvain Desbureaux1-1/+1
Forgot Mariadb PVC in previous commit (https://gerrit.onap.org/r/c/oom/+/94610). Change-Id: I9e3d96eab8b6d6ada7d2ab406a8e72249c909aa4 Issue-ID: CLAMP-488 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2019-10-11Align on release 4.1.3sebdet9-870/+21
Align the charts on the 4.1.3 clamp containers + fix the dcae parameters to https4 + remove old db files Issue-ID: CLAMP-513 Change-Id: I0429d1888f78d1a0f5ed7543cf0f9bb9cd77e652 Signed-off-by: sebdet <sebastien.determe@intl.att.com>
2019-09-16Bump up clamp to 4.1.2sebdet3-3/+3
Bump up the version of clamp to 4.1.2 to take the latest changes Issue-ID: CLAMP-506 Change-Id: If77b23f5263affd34cce121ab6b6d905195321f0 Signed-off-by: sebdet <sebastien.determe@intl.att.com>
2019-09-09Add frontend containersebdet12-2/+799
Add the frontend container as the main chart, and add clamp-backend as the a sub chart Issue-ID: CLAMP-486 Change-Id: Ib02562d608011047157b77b302902de86c0d954d Signed-off-by: sebdet <sebastien.determe@intl.att.com>
2019-09-05Merge "Fix OOM Clamp"Mike Elliott7-10/+20
2019-09-05Fix OOM Clampsebdet7-10/+20
Fix the image name and SQL for mariadb as it has been updated Issue-ID: CLAMP-467 Change-Id: I0bb9bf48b86a8eb3cc7a0f74dd5a5f20e46e8b44 Signed-off-by: sebdet <sebastien.determe@intl.att.com>
2019-09-02Merge "Move CLAMP Storage access to RWO"Alexis de Talhouët1-1/+1
2019-09-02Merge "Use nodePortPrefix variable in CLAMP-mariadb service template"Borislav Glozman1-1/+1
2019-08-29Move CLAMP Storage access to RWOSylvain Desbureaux1-1/+1
Today when deploying CLAMP with OOM, the PersistentVolumeClaim needs the "ReadWriteMany" (or "RWX") capability. According to Kubernetes Documentation (https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes), ReadWriteMany stands for "the volume can be mounted as read-write by many nodes". That means that a particular PVC needs to be read and written from many pods. That also means that your code takes that into account and do the work to avoid write at the same place at the same time. An issue on RWX mode is that most "official" storage driver from Kubernetes doesn't support it (13 over the 19 drivers doesn't support it, espacially OpenStack, Amazon and Google storage classes). CLAMP PVC is used only for one ES instance. Thus we don't need RWX. Change-Id: I3a17195bca4f0f01b5cdb0d8e803bb2a8ab2dd38 Issue-ID: CLAMP-488 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2019-08-02EarlyDrop and securityosgn422w6-4/+26
resolve security isue on kibana and release early drop CLAMP Issue-ID: CLAMP-419 Change-Id: I098f30d251f020470c0f1af1ce309a6a1a3b814d Signed-off-by: osgn422w <gervais-martial.ngueko@intl.att.com>
2019-07-17Use nodePortPrefix variable in CLAMP-mariadb service templatePawel Wieczorek1-1/+1
Issue-ID: OOM-1272 Change-Id: I5aaaf20a2bf53134ec18943ada701383ec37ab9e Signed-off-by: Pawel Wieczorek <p.wieczorek2@samsung.com>
2019-07-11Moving Helm Chart version for El AltoMike Elliott7-7/+7
Updating all helm chart versions to 5.0.0 for the El Alto release. Merge will be co-ordinated with the merge of a separate aai/oom patch. Please do not merge until this coordination has completed. Issue-ID: OOM-1980 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com> Change-Id: I31daaebeacea33565f13affd2fa28fb15fe948ba
2019-06-11Bump up clamp versionDeterme, Sebastien (sd378r)2-2/+2
Update clamp version to latest Issue-ID: CLAMP-408 Change-Id: I59b01cf3f9cdd37b5d0c48f63bea33d99040fea4 Signed-off-by: Determe, Sebastien (sd378r) <sebastien.determe@intl.att.com>
2019-05-31Bump up clamp versionDeterme, Sebastien (sd378r)2-2/+2
Update clamp version to latest Issue-ID: CLAMP-406 Change-Id: I05f5ae79a7856bffe671d806ab623313d6194727 Signed-off-by: Determe, Sebastien (sd378r) <sebastien.determe@intl.att.com>
2019-05-23kibana https onlyosgn422w6-3/+82
remove http access and allow only https for kibana UI Issue-ID: OJSI-147 Change-Id: I6026044c919abd51b8b6bd3b65f9552555c98e4c Signed-off-by: osgn422w <gervais-martial.ngueko@intl.att.com>
2019-05-10Update CLAMP images tagsChrisC2-2/+2
Update to RC images for clamp (4.0.1) Issue-ID: CLAMP-377 Change-Id: I3b890652ebd7bb045976c19263b0dadf3f291642 Signed-off-by: ChrisC <christophe.closset@intl.att.com>
2019-05-06Update DB with latestDeterme, Sebastien (sd378r)1-13/+13
Update DB with latest change for loop objects Issue-ID: CLAMP-368 Change-Id: Iad91362560a987a170a95e9b3959e1352296e610 Signed-off-by: Determe, Sebastien (sd378r) <sebastien.determe@intl.att.com>
2019-04-25Bump up CLAMP imageYang Xu2-2/+2
Change-Id: I6a49d62a097102e7b14707582a98720493fc422b Issue-ID: CLAMP-358 Signed-off-by: Yang Xu <yang.xu3@huawei.com>
2019-04-24Remove DCAE image from updateYang Xu2-2/+2
Change-Id: Ifa98f8610b0a96a28f3a3ded7cb65663e9455158 Issue-ID: INT-1042 Signed-off-by: Yang Xu <yang.xu3@huawei.com>
2019-04-15Update CLAMP mariadb version to 10.3.12ChrisC4-11/+91
Update to new mariadb version for Dublin along with a few SQL updates. Issue-ID: CLAMP-324 Change-Id: Ia0a095111332768af97d82f606d7c1048bfd812c Signed-off-by: ChrisC <christophe.closset@intl.att.com>
2019-04-04fixed logstash + es updateKrysiak Adam2-13/+6
Issue-ID: CLAMP-341 Change-Id: I5bd3cf20ec445e6972ce40f06f3d40e6056a1d43 Signed-off-by: Krysiak Adam <adam.krysiak@nokia.com>
2019-02-10Update Chart version for Dublin ReleaseMike Elliott7-7/+7
All charts are being bumped from 3.0.0 to 4.0.0 for the Dublin release. In addition the requirement.yaml files have been updated to allow for chart versions that include timestamp suffix. A following on patch will take care of changes to the OOM Makefiles to support injection of the timestamp versions. Change-Id: Ie03d86fad2027e975e8b9106e3a828e4335037cb Issue-ID: OOM-1642 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
2018-11-26Use flavors for resources in clamp deploymentSylvain Desbureaux4-25/+64
For Casablanca release, flavors have been set up for choosing the "right" resource requests and limits. Although the deployment is using the right way for that, clamp-xxx charts values.yaml was not. This commit makes values.yaml aligned with flavors Change-Id: I025965d3d7820345f8459a5c5821091a29b2c5c7 Issue-ID: CLAMP-250 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2018-11-14Sync docker tags with release manifestGary Wu2-2/+2
Sync docker tags with the release manifest from integration repo commit 6ac922392c49042b32df0171991da772ccec8571. Change-Id: I080588eb637c4df0791a2ffb61b56ff2d827bf63 Issue-ID: INT-663 Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
2018-11-09Update Clamp SQLDeterme, Sebastien (sd378r)2-3/+13
Update Clamp SQL for bugfix done on DCAE status check Issue-ID: CLAMP-246 Change-Id: I74933d62731e2ef764f488e27893ae37333f4116 Signed-off-by: Determe, Sebastien (sd378r) <sebastien.determe@intl.att.com>
2018-11-07Sync docker tags with release manifestGary Wu2-2/+2
Sync docker tags with the release manifest from integration repo commit 1e16c7e67d1fdeadab3789b07d6d2f47b7d0ffd7. Change-Id: If580d0000108ce9ff70ad128b9bc93bf4364376b Issue-ID: INT-663 Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
2018-11-05Update the SQLDeterme, Sebastien (sd378r)3-1/+130
Update SQL to preload CLamp mariadb Issue-ID: CLAMP-244 Change-Id: Ie7ed263acdc2ff492aced81b4109690e94d503a3 Signed-off-by: Determe, Sebastien (sd378r) <sebastien.determe@intl.att.com>
2018-10-26Sync docker tags with release manifestGary Wu2-2/+2
Sync docker tags with the release manifest from integration repo commit 73e35266be6609f1eb59d2de3bf819ebd3cb4a79. Change-Id: I8e79691e9d4cf27cc20082bd2dfbf6ee3bc7eef3 Issue-ID: INT-663 Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
2018-10-23fixing clusterIP service type errorsMandeep Khinda1-1/+1
If you try and change the service type from a nodeport to a cluster IP things break. We never really exercise this code path in testing but if you want to experiment with a totally internal network environment you need to be able to turn off node ports. Issue-ID: OOM-1475 Change-Id: I1a0f4b0a4c390f3353e1611b6002b93e54bb5044 Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-10-22Clamp: Use "common.repository" frameworkJulien Barbot4-4/+4
Change-Id: Ic1180781387700a8af36f84f619ffd66a5c02c34 Issue-ID: OOM-874 Signed-off-by: Julien Barbot <julien@barbot.org>
2018-10-18Sync docker tags with release manifestGary Wu2-2/+2
Sync docker tags with the release manifest. It is assumed that the release manifest is the "single source of truth" and that the versions in the helm charts are out of date. Change-Id: I2902e60b25f57409dd616780a626e63c92d26769 Issue-ID: INT-663 Signed-off-by: Gary Wu <gary.i.wu@huawei.com>