Agenda:

• Service upgrade status: @Tri Nguyen

  • with use of template selector, then deployment wouldn't join the mariadb cluster (not sure to know why)

    • proposal: don't change the selectors / metadata / ...

    • once it's merged into Frankfurt, update in order to be aligned with F release templates

  • JQ use: change to use it in the scripts. But jsonpath / gopath is fine too

  • SDNC:

    • Revise code for dgbuilder

      • data from dgbuilder is kept during release upgrade in DB so it should be good

    • @Dan Timoney answered that upgrade code is supposed to be idempotent so should  be good.

  • sdnc local cluster configuration is not well set in requirements.yaml

  • before ONAP upgrade, helm must be upgraded to v2.16.x (helm an tiller) as some new features are used with latest features of helm

• Password removal status: @Krzysztof Opasiak

  • policy: last one under rework

  • postgres:

    • finished but maybe an issue on postgres for VNFSDK?

    • maybe an issue with properly handling password with some special characters like '?' ?

• AAF template status: @Krzysztof Opasiak

  • dmaap dr still some work

  • elasticsearch also

  • portal not done

  • vid will be done with v1.16+ upgrade

• K8S v1.16+ status: @Sylvain Desbureaux

  • VID under work

  • Templates being worked:

    • readiness  template

    • securityContext templates for containers / pods

    • service account / role / role binding templates

      • question: do we allow to update the list by "configuration"? maybe for service mesh, so let's do it.

• Service Mesh PoC status: @Krzysztof Opasiak

  • a cluster has been provided by Orange, @Dominik Mizyn is migrating to this cluster

    • use Istio + keycloak

    • a Wordpress is deployed as test application to test JWT / mTLS / Ingress...

• Frankfurt release status: @Sylvain Desbureaux

  • smooth end of release

  • don't forget to clean up before merging into master and cherry pick frankfurt

  • use git clean -xfd when you switch between branches