Using AAF release Frankfurt dockers 90/107990/1
authorChrisC <christophe.closset@intl.att.com>
Wed, 20 May 2020 15:39:15 +0000 (17:39 +0200)
committerChrisC <christophe.closset@intl.att.com>
Wed, 20 May 2020 15:39:15 +0000 (17:39 +0200)
Uplifting AAF to 2.1.22 (Frankfurt)

Issue-ID: AAF-1127
Signed-off-by: ChrisC <christophe.closset@intl.att.com>
Change-Id: Ia371efeab9adbf99a8e0543d0c71adc028f6228e

kubernetes/aaf/charts/aaf-cass/values.yaml
kubernetes/aaf/charts/aaf-hello/values.yaml
kubernetes/aaf/values.yaml

index 3d9f21e..e347df2 100644 (file)
@@ -34,7 +34,7 @@ liveness:
   enabled: true
   port: tcp-cql
 
-image: onap/aaf/aaf_cass:2.1.20
+image: onap/aaf/aaf_cass:2.1.22
 
 config:
   cluster_name: osaaf
index aeb6590..786f0b0 100644 (file)
@@ -41,7 +41,7 @@ aaf_init:
 
 replicaCount: 0
 
-image: onap/aaf/aaf_hello:2.1.20
+image: onap/aaf/aaf_hello:2.1.22
 
 service:
   name: aaf-hello
index bedf243..cc97e98 100644 (file)
@@ -42,10 +42,10 @@ global:
 
   aaf:
     readiness: false
-    image: onap/aaf/aaf_core:2.1.20
+    image: onap/aaf/aaf_core:2.1.22
     aaf_env: "DEV"
     public_fqdn: "aaf.osaaf.org"
-    aaf_release: "El Alto"
+    aaf_release: "Frankfurt"
   # DUBLIN ONLY - for M4 compatibility with Casablanca
   #  aaf_locator_name: "public.%NS.%N"
   #  aaf_locator_name_oom: "%NS.%N"
@@ -57,7 +57,7 @@ global:
     cadi_x509_issuers: "CN=intermediateCA_1, OU=OSAAF, O=ONAP, C=US:CN=intermediateCA_7, OU=OSAAF, O=ONAP, C=US"
 
     config:
-      image: onap/aaf/aaf_config:2.1.20
+      image: onap/aaf/aaf_config:2.1.22
 
     service:
       fqdn: "aaf-service"