Agenda:
- k1.16+ capability! @Nokia Gang
- readiness:
- blueprints:
- core OK
- but some issue with FQDN
- open question: do we keep them as fixed or not?
- it's currently fixed but is it the good way?
- plan:
- daily "cncf" deployment will move to kubernetes 1.18 this week
- if everything OK, daily master will move with gating system end of next week
- last thing: update bootstrap container with cloudify being upgraded at the same time
- cassandra backup needs to be tested / repaired with new image
- helm3: @jakub latusek
- try to deploy common charts with helm 3
- some issues are seen
- mostly new linters issue (like having a capital letter in the chart name)
- comment that starts with '#' are interpreted by helm
- "empty" files (only with #) will get checked by helm linter and will miserably fail
- so needs to enclose headers / comments with '{{/* */}}'
- common secret template issue:
- different release name for (having a dash instead of camelCase)
- but dash is "helm deploy" forbidden...
- things to do:
- make common work
- check that content is the same
- check other charts
- change doc for helm charts repository start (chartmuseum for example)
- see if we still need helm deploy/undeploy
- SO/AAI/SDNC issue: Sylvain Desbureaux
- proposal: revert the two faulty reviews
- shared mariadb: Rajendra Prasad Mishra
- comments from Krzysztof Opasiak being worked on
- issue with table creations
- close to be merged
- passwords with DBs: Krzysztof Opasiak
- fix for SO is pending
- clamp fixed has been merged
- password complexity in review (in F)
- bug in VID prevents merge on fix for print (%s instead of %d)
- upgrade: Tri Nguyen
- M4: Sylvain Desbureaux
- administrative task to do
- committers
- service mesh
- jenkins root cause: Krzysztof Opasiak
- logging work: Dominik Mizyn
- lots of STDOUT enabling
- logback.xml file in OOM repo are not really used for a lot of components...
{"serverDuration": 812, "requestCorrelationId": "00b9066dd0220adb"}