summaryrefslogtreecommitdiffstats
path: root/kubernetes/sdc/charts/sdc-cs
AgeCommit message (Collapse)AuthorFilesLines
2018-04-25Adding sdc-onboarding-be to OOMMandeep Khinda5-55/+14
-adding sdc-onboarding-be chart -sdc-cs and es are now in a cluster format -using the sdc provided ready probe script for readiness -increasing the initial delay as per sdc project team k8s specs -fixed logging bugs. logs for be, fe, onboard-be are now in /var/log/onap/sdc/blah -sdc-be readiness health check is failing which prevents sdb-be from becoming "ready". -the commit that changes the template is: Add cluster resiliance support (c033cdce906efc3b6ccd1d2f45544af47e328ed4) Issue-ID: OOM-1002 Change-Id: Ib231cb1e7daa287a41e04db95528edecbdbbf7bc Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-04-24Make all services independent of helm Release.NameBorislavG3-7/+8
Issue-ID: OOM-906 Change-Id: Ic65127d3981cb0a696c784392cab59fbf06b1e66 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
2018-04-20fixing sdc health checkMandeep Khinda3-19/+46
-Basically compared docker_run.sh from sdc master branch with charts/values in OOM -disabling sdc-kb liveness until we tune the timing of it Issue-ID: OOM-964 Change-Id: I7447eed47c919d5d64786f45e01b5f2a3bc490a0 Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-04-16Update readiness-check versionBorislavG1-1/+1
Readiness check version is not sinchronized in many pods This causing deployment failures. Issue-ID: OOM-936 Change-Id: Ieef91df17836adcdf24db536440d0a1624a50591 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
2018-04-01SDC chart hotfixkj2-0/+4
Issue-ID: OOM-851 Change-Id: I431a54d7b218a7271efba8496a71412085052959 Signed-off-by: kj <keren.joseph@amdocs.com>
2018-03-29adding license to SDC chart templatesMandeep Khinda8-1/+99
-missed adding it to the original review before it was merged Issue-ID: OOM-838 Change-Id: I04b515e2f4c58a14b4b4194e59e160b1f8534bc6 Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-03-28standardizing SDC helm chartsMandeep Khinda10-0/+408
all pods come up robot health reports HTTP 500 -> mostly due to missing dmaap resolving filebeat merge conflict addressing CI comments do we need a pv/pvc for the logs? Issue-ID: OOM-747 Change-Id: Id6f1e57fdaf3cd6d9f75e8bc1e5bfde39b91235e Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com> Signed-off-by: Areli Fuss <af732p@intl.att.com> (cherry picked from commit fe3e499547c91eadd71bde630594720b918c2af9)