summaryrefslogtreecommitdiffstats
path: root/kubernetes/aaf/charts/aaf-service/templates
AgeCommit message (Collapse)AuthorFilesLines
2020-05-04[AAF] v1.16+ compatible templatesSylvain Desbureaux2-153/+6
Use the different "common" templates in order to create consistent and v1.16+ compatible templates for the different resources of AAF Issue-ID: AAF-1122 Issue-ID: OOM-1971 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: Iefc1391211a69b6584ea127066ce430d4f5eb389
2020-04-07AAF OOM 2.1.20ChrisC1-0/+17
Cleaned up up configs, JDK11 fixes, Hello and Agent works, now a model for Apps non-root fix Issue-ID: AAF-1081, AAF-1102 Signed-off-by: Instrumental <jgonap@stl.gathman.org> Signed-off-by: ChrisC <christophe.closset@intl.att.com> Change-Id: I4947075029db8abd7d2072b6b82064af8e2daa3e
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-11Merge "[AAF] Use global storage templates for PVC"Borislav Glozman1-2/+2
2019-12-05[AAF] Use global storage templates for PVCSylvain Desbureaux1-2/+2
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 modified statefulset deployment so they can use their own PVC instead of writing into a specific directory inside I've also set to 'emptyDir' volumes when persistence is not enabled (except for aaf-config-pvc and aaf-status-pvc, which means that AAF will still not work when persistence is disabled). Change-Id: I05f133f058ebd9678df9ac0b7ef32bb43689e94f Issue-ID: OOM-1227 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2019-11-27Add ingress controller support to AAFLucjan Bryndza1-0/+4
Change-Id: Ie69b9dac533ed2af80645e6d65318b6b4e81cbd3 Issue-ID: OOM-2170 Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
2019-08-06AAF 2.1.15 DockersInstrumental1-3/+8
Issue-ID: AAF-902 Change-Id: I3a83eee98dfeb7fb9751019faf618897dbc9d34f Signed-off-by: Instrumental <jonathan.gathman@att.com>
2019-05-01Apply Cert changesInstrumental2-50/+57
Issue-ID: AAF-822 Change-Id: I3185d827f3f67cb177534f7c7f3281375b77c613 Signed-off-by: Instrumental <jonathan.gathman@att.com>
2018-10-25update OOM for 2.1.6Instrumental1-1/+1
Issue-ID: AAF-571 Change-Id: I95f1f9c1604c36bc76eb556c7f35fdb8caceba57 Signed-off-by: Instrumental <jonathan.gathman@att.com>
2018-10-17Recommended AAF/OOM ChangesInstrumental1-21/+23
This incorporats Mike E's changes as well as recommended changes from Abandoned 70511 (merges from multiple machines got too hard.) Made Olaf recommended changes. Changed to non-SNAPSHOT in anticipation of LF releasing this morning Put Versions back to "2.1.5-SNAPSHOT" Brian F reminded me that GWu's scripts handle version changes for Envs. Issue-ID: AAF-557 Change-Id: I3e81a9c65df356d1d27b0d453e09c9ed3a81f803 Signed-off-by: Instrumental <jonathan.gathman@att.com>
2018-10-11refactor AAF casablanca chartsMandeep Khinda1-20/+13
Issue-ID: AAF-539 Change-Id: Id1f263d526ef5fa88c6cd25f7ed1779d3a0cd2ee Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-09-25Updating charts to use common resource templateMandeep Khinda1-1/+1
Issue-ID: OOM-1145 Change-Id: I1510339a820802554b6e8b9a201619ef66be17a0 Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-06-07Remove stderr/stdout redirection from CommandInstrumental1-1/+1
Issue-ID: AAF-353 Change-Id: Ief7a3dda7160e385c15ed0be7e158c7de3af8cdd Signed-off-by: Instrumental <jonathan.gathman@att.com>
2018-05-07AAF ChartsMahendra Raghuwanshi2-0/+155
-PS3-MK -renaming charts to remove hyphen -refactoring service name configuration. It wasn't quite correct the way it was. It was taking the chart name as the service name and not using the values.yaml from the top level chart as intended. -Jonathan asked to name the main app service "aaf-service and cassandra to "aaf-cass" as this is what is in the cert -squashed https://gerrit.onap.org/r/#/c/45923/1 into this commit. -updated robot to the latest settings Robot tests are failing but all pods come up. I think this can be merged and the AAF team investigate the robot health issue in a running system -PS4-MK -reverting sms changes and taking the latest from master -removing repository from the global section of the aaf values. -this was causing all images to be pulled from nexus3.onap.org which was failing to pull images that come from docker hub. There is supposed to be a proxy through nexus3 to dockerhub but maybe we are missing something. -PS5-MK -removing nodeports from non gui related charts. There are conflicts -PS6-Kiran -Adding imagepullsecrets for aaf-sms-vault subchart -updated image repository to pull from nexus3 -tested and works now and should fix the pull errors -PS7-Kiran -Previous patch picked up a couple of unintended changes -Reverting them -PS8-MK -removing names from identities -using https for robot test Issue-ID: OOM-930 Change-Id: I98f40ef5af03dda73aebf12f6fa48d928915ab34 Signed-off-by: Mahendra Raghuwanshi <mahendra.raghuwanshi@amdocs.com> Add Beijing CQLs into OOM Issue-ID: AAF-114 Change-Id: I2c2d46738ba0885c41f710997d4b212b6ce4d2de Signed-off-by: Instrumental <jonathan.gathman@att.com> Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com> Signed-off-by: Kiran Kamineni <kiran.k.kamineni@intel.com>