Agenda

• Kubernetes Stable API support: @Grzegorz Lis (Nokia) @Daniel Milaszkiewicz

  • Latest master is now OK for 1.18!

  • @Sylvain Desbureaux will move on of the daily on 1.18 this week (this one uses storage classes and ingress)

  • gating will move to AKS if everything OK

• OOM on dual stack Kubernetes: @Daniel Milaszkiewicz @Grzegorz Lis (Nokia)

  • if we want service on IPv6, need to create a new service (for IPv6). "IPv4" service cannot be used for both stacks.

  • test on bulk pm on dual stack

• Helm 3 support: @Jakub Latusek

  • most of components in OOM

  • skipped

    • sniro-emulator, this is OK (simulator of an homing service for AT&T only)

    • oof : not working on Jakub environment even with helm2

  • common.fullname: patch doesn't work (line https://github.com/onap/oom/blob/master/kubernetes/common/common/templates/_name.tpl#L56 doesn't work) @Krzysztof Opasiak ("if condition is always false")

• STDOUT logs: @Dominik Mizyn

  • lot of work done so far

• Seamless upgrade: @Tri Nguyen

  • review is needed from @Sylvain Desbureaux

  • comments from @Krzysztof Opasiak to be addressed

• AAF SMS issue on some pods: take a look here to see logs of owrking deployment: https://logs.onap.org/onap-integration/daily/onap_daily_pod4_master

• SO issue: @Sylvain Desbureaux

  • 1.7.1 is not working as expected

  • latest SDNC seems to have trouble

  • e2e test from integration are compatible so hard to see

  • plan:

    • use python-onapsdk on integration with GR API: ongoing

    • check where the issue is on SDNC

    • wait for 1.7.3 on SO side (two bugs found by @damian.nowak )

    • a lot of SO MR on OOM that are stalled because of that

• issue: ONAP in namespace different than onap, it doesn't work

  • lots of pods expect "onap" as namespace when calling other pods

• service mesh: @Sylvain Desbureaux

  • kind of stuck now...

  • how we can coordinate with multi tenancy project