summaryrefslogtreecommitdiffstats
path: root/kubernetes/sdc/templates
AgeCommit message (Collapse)AuthorFilesLines
2020-02-01[ONAP-wide] Replace .Release.Name with common.releaseKrzysztof Opasiak2-6/+6
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-17Secure FE communications to the workflow backendIlanaP1-0/+6
Update of the workflow fe and be charts to secure the communications and to start the backend server is https mode with a secured connection to SDC Issue-ID: OOM-1954 Signed-off-by: IlanaP <ilanap@amdocs.com> Change-Id: Ia3c4c714e317b8f8b6b4ee9245daa50eea50275f Signed-off-by: IlanaP <ilanap@amdocs.com>
2018-09-14sdc portal Config Map Labellingtoshrajbhardwaj1-0/+10
Issue-ID: OOM-1390 Change-Id: I8fe0dbde62cb8d88ec18321078ea6740bad8524a Signed-off-by: toshrajbhardwaj <toshrajbhardwaj@gmail.com>
2018-08-30Apache2 License additiontoshrajbhardwaj2-0/+2
Issue-ID: OOM-1306 Change-Id: I1a617718006ee845d675fead74ce075c3390ac2f Signed-off-by: toshrajbhardwaj <toshrajbhardwaj@gmail.com>
2018-04-25Adding sdc-onboarding-be to OOMMandeep Khinda1-0/+31
-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.NameBorislavG1-1/+1
Issue-ID: OOM-906 Change-Id: Ic65127d3981cb0a696c784392cab59fbf06b1e66 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
2018-03-29adding license to SDC chart templatesMandeep Khinda1-0/+14
-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 Khinda11-821/+15
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)
2018-03-22Fix license for PV and PVC yamlsMike Elliott1-0/+2
When conditions are used at the start of the yaml the hashed (#) comments of the license are not parsable by the json parser. There license comments have been wrapped in {{/* */}}. Change-Id: I16c539ae4280f8ecacfdedb1f8caad894f3a081f Issue-ID: OOM-821 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
2018-03-22License addition in all yamlsvaibhav_16dec10-0/+140
Issue-ID: OOM-821 Change-Id: I627ac962afe8cd6bf2859a30a0e88f6c9ac89d34 Signed-off-by: vaibhav_16dec <vaibhav.chopra@amdocs.com>
2018-03-01Run all components in one namespaceBorislavG10-21/+21
Change-Id: I5fcd4d577c1fda4de27842807c7cf7a5d372756e Issue-ID: OOM-722 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
2018-02-25sdc persistence folder parametrizationkerenj6-9/+9
Issue-ID: OOM-145 Change-Id: Ife998e01fcfa9455b7a35674909df8a338f92a59 Signed-off-by: kerenj <keren.joseph@amdocs.com>
2018-02-07Config seg sdc deploymentPramod8-20/+90
Issue-ID: OOM-550 Signed-off-by: Pramod <pramod.kumarsharma@amdocs.com> Change-Id: Ibad8a16fb289ddd4260be5cce0c787e4de212a97
2017-12-15Fix SDC-ES Connection refusedMunir Ahmad1-6/+1
Signed-off-by: Munir Ahmad <munir.ahmad@bell.ca> Issue-ID: OOM-515 Change-Id: Ia87da1e2f24aa36e9f3ce43404ee4f1ff8635a79
2017-11-22Update annotations to spec for sdcvasundhra4-137/+86
Issue-ID: OOM-406 Change-Id: Ib56669c7d0919700c5a7247195564a789329ee3c Signed-off-by: vasundhra <vasundhra.choudhary@amdocs.com>
2017-11-06Fix SDC-FE logging confiurationBorislavG1-1/+3
SDC-FE logs location was missing /var/log/onap Issue-ID: OOM-403 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com> Change-Id: Iec13970609981c94c7da85b56c78cea11846ade8
2017-10-29Add option to disable specific deploymentsyuryn7-0/+22
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 componentsyuryn2-0/+50
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ët2-50/+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 Hassid2-0/+50
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-15Add service endpoint annotation for SDCHuabingZhao1-0/+31
Issue-Id: OOM-223 Change-Id: Ie1ad56e163bc00b91465e25359d272122ae8ebfd Signed-off-by: HuabingZhao <zhao.huabing@zte.com.cn>
2017-09-14Containers time zone syncyuryn5-0/+5
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-13Fix persistent volumes for multiple onap instancesBorislavG1-3/+3
Deploy multiple namespaces fails due to existing persistence volumes. "persistent-volume "appc-db" already exists" Need to change all persistent volume names to include namespace. Change-Id: I40a3048bef14f813b133ea75e2f664f669183e82 Issue-ID: OOM-294 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
2017-09-06Persistent volumes for Database storageBorislavG2-2/+32
Addition of persistent volumes for all DBs including persistence of policy mariadb (with initial configuration data) Change-Id: I029e724c3f8bba7fe3599b0955a4a3d213c08163 Issue-ID: OOM-268 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
2017-09-05Merge "NodePort Helm Parametrization"Yury Novitsky1-4/+4
2017-09-01fixing failed SDC FE and BE startupMandeep Khinda2-10/+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-31NodePort Helm Parametrizationkerenj1-4/+4
parameterization of node ports, and create/delete update to fix multi ONAP instances creation(in diff NS). Issue-ID: OOM-52 Change-Id: Iaa3f5bc43f70b95cdc349389e25ef8b804a7a329 Signed-off-by: kerenj <keren.joseph@amdocs.com>
2017-08-25refactor helm files to use namespace prefixMandeep Khinda6-33/+33
-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 Parameterizationkerenj6-0/+531
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>