summaryrefslogtreecommitdiffstats
path: root/kubernetes/sdc/templates/sdc-be.yaml
AgeCommit message (Collapse)AuthorFilesLines
2017-11-22Update annotations to spec for sdcvasundhra1-49/+31
Issue-ID: OOM-406 Change-Id: Ib56669c7d0919700c5a7247195564a789329ee3c Signed-off-by: vasundhra <vasundhra.choudhary@amdocs.com>
2017-10-29Add option to disable specific deploymentsyuryn1-0/+2
Add option to disable any deployment by using conditions in helm templates. Each deployment will get helm parameter - boolean flag allowing to disable it. The flags can be listed in the custom values.yaml file that can be passed to the createAll script with '-v' command line option. Change-Id: I32b795de46c72915c2201c94c23f4e061971bb56 Issue-ID: OOM-380 Signed-off-by: yuryn <Yury.Novitsky@Amdocs.com>
2017-10-13fixing SDC logback mounting defectMandeep Khinda1-1/+5
sdc-be now starts and robot passes healthcheck ---------------------------------------- Basic ASDC Health Check | PASS | ---------------------------------------- Note that I did not verify whether the logging function is working - priority for this issue is to get SDC running. Issue-ID: OOM-359 Change-Id: Ic810109878aa003c54350a6e70a4aeeea9b2f0ea Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2017-09-27added filebeat to all componentsyuryn1-0/+24
Deployment of: filebeat containar for each relevant component + chown of log dir to root - prevents filebeat complaining about filebeat file + ecomp web app renamed onap - fixed dep-pap.yaml + fixed multiple volumeMounts in vid-server Change-Id: I74f8f2abd5feeba1d37b044d2a023674fd41c994 Issue-ID:OOM-110 Signed-off-by: yuryn <Yury.Novitsky@Amdocs.com>
2017-09-26Revert "added filebeat to all components"Alexis de Talhouët1-24/+0
Pods aren't starting properly. Let's not take any risk, so reverting. 3m 18s 4 kubelet, kubernetes-5 spec.containers{vid-server} Normal Killing Killing container with id docker://vid-server:FailedPostStartHook This reverts commit 4ca69ea2b6a2aaaf0974953a3c3dec7694fdfcb0. Deployment of: filebeat containar for each relevant component Issue-ID:OOM-110 Change-Id: I7953ac3b0e2a4ecbdd1a7d2a48cb9a1964bf08ab Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
2017-09-24added filebeat to all componentsItay Hassid1-0/+24
Deployment of: filebeat containar for each relevant component Issue-ID:OOM-110 Change-Id: I3605a975ee9dbe3e34b8fa6b17fef52e9d29b975 Signed-off-by: Itay Hassid <itay.hassid@amdocs.com>
2017-09-14Containers time zone syncyuryn1-0/+1
Make sure time zones on the containers are in sync with the hosting machines Change-Id: Ie22608bda63cbcdf564f73adcdd3e829afad05ca Issue-ID: OOM-299 Signed-off-by: yuryn <Yury.Novitsky@Amdocs.com>
2017-09-01fixing failed SDC FE and BE startupMandeep Khinda1-5/+0
- a new sdcfe/be image was failing because of a file conflict with the keystore file that was mounted into the pods. fix was to remove mount and let chef do its thing inside the pods Issue-ID: OOM-259 Change-Id: Ib7937da71adf0a20c90d6efca71ccfb7c550f42d Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2017-08-25refactor helm files to use namespace prefixMandeep Khinda1-7/+7
-removed the full namespace from each template. better lets us reuse variables. -made secret end up in a configurable namespace -fixed some bugs where secrets were missing -updated createAll and delete to make use of namespace prefix removing the need for seds to replace the word onap. *** all containers at this point come up in my env. except for aai model loader which is failing cause its still at 1.0 and its trying to talk to a 1.1 sdc and it doesnt auth properly. *** Issue-ID:OOM-215 Change-Id: I15815a01469786a391e272fde4bdaa53ff48091c Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2017-08-24sdc K8S-Helm Parameterizationkerenj1-0/+113
changed sdc k8s deployment to support helm parameterization. updated create/delete for helm only Issue-ID: OOM-52 Change-Id: Ic7fb17fcf5be5813b0a0c54299cdf0d0417e8a76 Signed-off-by: kerenj <keren.joseph@amdocs.com>