aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/common/common/templates/_serviceMesh.tpl
AgeCommit message (Collapse)AuthorFilesLines
2023-05-25[COMMON] Update Common Authorization PolicyAndrewLamb1-1/+1
Change app label to use same common.name as the common.labels use. Issue-ID: OOM-3148 Change-Id: Id1a27326df89883c96f6c2f5d3019dd29c19c74d Signed-off-by: AndrewLamb <andrew.a.lamb@est.tech>
2023-04-21[POLICY][COMMON] Create Authorization Policies for PolicyAndrewLamb1-2/+2
Policy- Add initial authorized serviceaccounts for each sub component service Common- Change authorizationpolicy to match on the label app Issue-ID: OOM-3139 Change-Id: I411877b933d6dfcbdee633f1440d16c9658438e5 Signed-off-by: AndrewLamb <andrew.a.lamb@est.tech>
2023-04-18[COMMON] Fix Authorization Policy TemplateAndrewLamb1-4/+2
Fix for: no matches for kind AuthorizationPolicy, when trying to install on deployment with no istio. Issue-ID: OOM-3163 Change-Id: I3e0be55d78e6c88655eeaf267c25b8e6747c5b3c Signed-off-by: AndrewLamb <andrew.a.lamb@est.tech>
2023-03-21[COMMON][SO] Create authorization policy templateAndrewLamb1-0/+81
Create template for istio authorization policies Issue-ID: OOM-3148 Change-Id: I081288e8e9b0e8347ee6fd0d656398126826c273 Signed-off-by: AndrewLamb <andrew.a.lamb@est.tech>
2022-01-25[SDC] Service Mesh Compliance for SDCothman touijer1-2/+31
Adding basic requirements for Service Mesh Compliance within SDC. Change-Id: Ib9104ef2e8b6daf0b9b529288cee158b297ce9e4 Issue-ID: OOM-2253 Signed-off-by: rope252 <gareth.roper@est.tech> Signed-off-by: othman touijer <othman.touijer@soprasteria.com>
2021-09-13[AAI] Service Mesh compatibilityosk114611-0/+12
This patch makes AAI to work on service mesh by removing https calls from everywhere. It allows also to use AAI on an environment without need of TLS. Issue-ID: OOM-2670 Signed-off-by: Ondrej Frindrich <ondrej1.frindrich@orange.com> Change-Id: I19adabc7b33c1ada243ec16f77dbf8fde19b1386
2020-03-25[COMMON] Optimize common secret templateKrzysztof Opasiak1-1/+1
It turned out that our current implementation of common secret template is really heavy which makes onap linitng extremely long. To improve the situation let's introduce some results caching instead of processing templates over and over. For now we cannot simply replace common secret template because in mariadb-init we generate list of secrets on the fly so we will need to revisit this fragment later. Whole series of patches managed to reduce ONAP linting time to 40 mins. Issue-ID: OOM-2051 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: Id2e743147afa37290df19b73feee67621f13f67c
2020-03-06[COMMON] Handle TLS/Non-TLS for ServiceSylvain Desbureaux1-0/+27
Current service and headlessService templates doesn't handle the fact that out of cluster ports must be TLS encrypted only. With a new (backward compatible) DSL, this is now possible. In values.yaml, all ports in service part with port AND plain_port will have the ability to be HTTP or HTTPS depending on the context. Per default, they'll be HTTPS. TLS choice will be done according this table: | tlsOverride | global.tlsEnabled | global.serviceMesh.enabled | global.serviceMesh.tls | result | |-------------|-------------------|----------------------------|------------------------|--------| | not present | not present | not present | any | true | | not present | not present | false | any | true | | not present | not present | true | false | true | | not present | not present | true | true | false | | not present | true | any | any | true | | not present | false | any | any | false | | true | any | any | any | true | | false | any | any | any | false | Service template will create one or two service templates according to this table: | serviceType | both_tls_and_plain | result | |---------------|--------------------|--------------| | ClusterIP | any | one Service | | Not ClusterIP | not present | one Service | | Not ClusterIP | false | one Service | | Not ClusterIP | true | two Services | If two services are created, one is ClusterIP with both crypted and plain ports and the other one is NodePort (or LoadBalancer) with crypted port only. Issue-ID: OOM-1936 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: If766dd73132022d1a6e578fd36113c461bb91ea5