summaryrefslogtreecommitdiffstats
path: root/kubernetes/clamp/charts/clamp-dash-es/values.yaml
AgeCommit message (Collapse)AuthorFilesLines
2019-09-05Merge "Fix OOM Clamp"Mike Elliott1-1/+1
2019-09-05Fix OOM Clampsebdet1-1/+1
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-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 securityosgn422w1-2/+2
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-04-04fixed logstash + es updateKrysiak Adam1-1/+1
Issue-ID: CLAMP-341 Change-Id: I5bd3cf20ec445e6972ce40f06f3d40e6056a1d43 Signed-off-by: Krysiak Adam <adam.krysiak@nokia.com>
2018-11-26Use flavors for resources in clamp deploymentSylvain Desbureaux1-6/+16
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-10-09Migrate ELK to 6.1.3 OSSac25501-1/+1
+ add logstash configuration for a 2nd aggregated index + use new restore scripts for restoring dashboards Change-Id: I9176fa3b551591fdaf968e5b2496d510581aca22 Issue-ID: CLAMP-222 Signed-off-by: ac2550 <ac2550@intl.att.com>
2018-09-05Apache 2 license addition for clampMukul1-2/+1
Issue-ID: OOM-1369 Change-Id: I7ad1f9654f90ffe9c67dcf567c3ca694366bc66a Signed-off-by: Mukul <mukul.joshi@amdocs.com>
2018-06-01Fix OOM settingsDeterme, Sebastien (sd378r)1-8/+8
Fix CLamp settings in CLAMP, like resource allocation Issue-ID: CLAMP-174 Change-Id: I6c95ef8773d459edf7dc7577aa8ea9884176100b Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com>
2018-05-17Merge "ELK version bump"Mike Elliott1-2/+2
2018-05-17Fix clamp changing persistence permissionsBorislavG1-0/+1
There is a missing parameter in clamp values.yaml: persistence.mountSubPathLogs, which causes /dockerdta-nfs/ReleaseName directory to be come with permissions 777. Issue-ID: OOM-1086 --- modified: clamp/charts/clamp-dash-es/values.yaml Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com> Change-Id: Iddd80f77e7e42b06dd4b55c302d4d45127ea1b72
2018-05-17ELK version bumpac25501-2/+2
Issue-ID: CLAMP-162 Change-Id: I7174d1a18452e444d6806564662ab3d2ba0bc252 Signed-off-by: ac2550 <ac2550@intl.att.com>
2018-05-15Add clamp dashboard chartsac25501-0/+116
Change-Id: I851750c2c394fad4c5187e2a18cfa0460a16c729 Issue-ID: CLAMP-154 Signed-off-by: ac2550 <ac2550@intl.att.com>