summaryrefslogtreecommitdiffstats
path: root/kubernetes/common/mongo/values.yaml
AgeCommit message (Collapse)AuthorFilesLines
2020-11-20[GENERIC] move from registry.hub.docker.com to docker.ioSylvain Desbureaux1-1/+1
`registry.hub.docker.com` needs authentication now, in contrary to previous behavior. As OOM deployments is unauthenticated when using docker hib repository, all OOM deployments is broken. `docker.io` seems to be still OK with unauthenticated requests so let's move to this endpoint. Issue-ID: OOM-2636 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: Iea81b882d347124af22b0a9c408081706b1c6c6d
2020-09-23[COMMON] Add limits to mongo statefulsets.Sylvain Desbureaux1-8/+16
Having limits is important in order to have safe deployment. mongo didn't had one so let's add them. Issue-ID: OOM-2230 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: I4791b924693e4e1eaac14077d4f30e3d29228779
2020-09-09[COMMON] Make mongo run as non-rootKrzysztof Opasiak1-0/+4
Use our helper template and k8s features to make mongodb run as a non-root user as per Guiling requirements. Issue-ID: DCAEGEN2-2424 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: I44bc079a2cc49dc1b0f1da88e220290098e909d5
2020-09-04[GENERAL] Use readiness container v3.0.1Sylvain Desbureaux1-2/+1
Readiness container v3.x and up are now present in ONAP main repository. They're also not using root user anymore and then script path has changed. Finally, "job_complete" script has been integrated in main "ready" script. As those changes are significant, we must upgrade all the components at once. Depends-On: I5afa83892043f4844afe12e61724a8d368a9f2e0 Issue-ID: OOM-2545 Signed-off-by: Grzegorz Lis <grzegorz.lis@nokia.com> Change-Id: I0b4eb5dd86390273532d67d0a9696e1cfcadf110
2019-12-05[Common] Use global storage templates for PVCSylvain Desbureaux1-7/+0
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 aligned the PV creation of the different charts. I've also aligned the PVC creation of the different charts. I've removed unused mysql chart and (badly) used nfs-provisioner chart. I've also make cassandra backup work with dynamic PV (but RWX only for now). Change-Id: I0ea3f8c7514ca648d94b6c682684c06b822bbe0a Issue-ID: OOM-2229 Issue-ID: OOM-2228 Issue-ID: OOM-2227 Issue-ID: OOM-1227 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2019-08-29Move Storage access to RWOSylvain Desbureaux1-1/+1
Today when deploying NBI 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). MongoDb PVC is used only for one Mongo instance and it's the same for maria. Thus we don't need RWX Change-Id: I4d54cd7853778d8ba6c83551a211abe34d383382 Issue-ID: EXTAPI-305 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2019-04-11Bump version of Mongo and Mariadb for NBISylvain Desbureaux1-1/+1
Change-Id: Ib6042ee657415ec94d5c8acdd23a2ef1b5438a93 Issue-ID: EXTAPI-213 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2018-05-17Add External Interface NBI project into OOMSylvain Desbureaux1-0/+119
NBI (North Bound Interface) is one of the new project added for Beijing release. Features added ============== MongoDB common chart -------------------- Ability to start a mongo container, with a chart consistent with other common charts (readiness, liveness, persistence, resources, nfs, service, ...). Specific configuration: * name of the db to create if needed NBI chart --------- Ability to start a mariadb container, with a chart consistent with other common charts (readiness, liveness, persistence, resources, nfs, service, ...). Specific configuration: * name of the db to create if needed * name of the user that has access to the db * password of the user that has access to the db * root password of the database Ability to start a NBI container, with a chart consistent with other common charts (readiness, liveness, persistence, resources, nfs, service, ...). Specific configuration: * log level * cloudOwner * ecompInstanceId * openStackRegion * openStackServiceTenantName * sdc_authorization * aai_authorization * so_authorization ONAP chart ---------- Added a requirement on NBI chart, possibility to enable/disable and configuration to push to the chart. Current Status ============== - [*] adding a common chart for mongodb - [*] make mongo chart compiling - [*] testing the mongodb common role - [*] creating a mariadb chart inside nbi helm - [*] testing the mariadb chart - [*] make mariadb chart compiling - [*] make nbi use these charts - [*] make nbi chart compiling - [*] test the whole solution - [*] create a service for nbi Change-Id: I8dd3e79768c83b1553a05c892cf418f840931255 Issue-ID: EXTAPI-54 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>