...
- DCAE: tls automatic retrieval Vijay Kumar Jack Lucas Krzysztof Opasiak
- certInitializer vs already deployed method from DCAE
- OOM Team position: would be nice to move to certInitiliazer
- DCAE: two types of component (one deployed through charts, the others deployed through cloudify)
- DCAE "own" init container wraps "AAF container" + change cert format and names
- Proposal: move to certInitializer for helm components + another container (if needed)
- DCAE init container - https://git.onap.org/dcaegen2/deployments/tree/tls-init-container
- certInitializer vs already deployed method from DCAE
- DCAE: STDOUT. list of components complying/partially complying/not complying complying Vijay Kumar
- v1.17: Grzegorz Lis (Nokia), Daniel Milaszkiewicz, Magdalena Biernacka, Krzysztof Kuzmicki
- plan: use >=v1.15 and >=v1.16 kubernetes APIs
- most of common templates have a merge request to be v1.17 compatible
- mariadb upgrade scripts: Marat Salakhutdinov Tri Nguyen https://gerrit.onap.org/r/c/oom/+/109627
- network name gen: review to be done
- maintenance releases
- elalto: 3 reviews to go
- frankfurt : >5 reviews to go
- release notes
- certInitializer and custom certificates: Sebastien Premont Krzysztof Opasiak
- trustore "all" is given in certInitializer helm chart
- proposal:
- change certInitializer and add an init container where we add the custom certificates
- release note to be done: kubernetes underlying OS must use kernel >=4.9 with overlayfs (with example on Ubuntu with must be >=18.04) Marat Salakhutdinov Krzysztof Opasiak
- DMaaP helm issue: DMaaP Helm Config Map is too big ematpil Sylvain Desbureaux we have to work on this
...