...
- Release Managment tasks to be completed
- What tasks and who will do it ?
- Branch Jakarta
- Writing Release Notes (Jakarta Documentation)
- Jakarta Release Key Updates (→ should we mention Strimzi ?)
- Service mesh:
- Need a global requirement for Kohn (https://jira.onap.org/projects/REQ) → discussed with David (old REQ
)Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-368 - Existing epic JIRAs:
- Need a global requirement for Kohn (https://jira.onap.org/projects/REQ) → discussed with David (old REQ
- Istio Setup Update Andreas Geißler
- Test-Environments
- ONAP:
kubespray_version: release-2.17
helm_release: v3.6.3
kubernetes_release: v1.21.5
istio_release: "1.10.2"
- TNAP:
kubespray_version: v2.18.1
helm_release: v3.7.1
kubernetes_release: v1.22.5
istio_release: "1.13.1"
- ONAP:
- Open patches:
- https://gerrit.onap.org/r/c/oom/+/128335 [STRIMZI] Make Strimzi ServiceMesh compatible
- https://gerrit.onap.org/r/c/oom/+/128989 [AAF] Make AAF ServiceMesh compatible
- required as workarround for DMaaP issue
- https://gerrit.onap.org/r/c/oom/+/128715 [DMAAP] DMaaP ServiceMesh compatibility
- Issues with Message-router (dependency to AAF when configuring the SASL connection to Kafka)
- Workarround (deploy AAF with special options and enable AAF for DMaaP)
- https://gerrit.onap.org/r/c/oom/+/128994 [SO] Service mesh compatibility
- includes now https://gerrit.onap.org/r/c/oom/+/124231 → can be "abbandoned"
- not yet tested:
- https://gerrit.onap.org/r/c/oom/+/128992 [CDS] Service mesh compatibility
- https://gerrit.onap.org/r/c/oom/+/128543 [POLICY] Service Mesh Compliance for Policy
- needed CR:
- [NBI] Service mesh compatibility
- Fiachra Corcoran is proposing that components move to Kafka native
- Kafka native clients would not use service mesh for Kafka, but other traffic would go through the sidecar, using the mesh
- Test-Environments
...