...
- Page 2: "Problem: Has ONAP Montreal finished its release cycle?"
- yes, sign-off at 14.12.2023
- Page 3: "By default, the message router no longer exposes NodePort We expose this port for testing"
Could be also exposed via ingress by enabling it in values.yaml of DMAAP:
Code Block message-router: ingress: enabled: true service: - baseaddr: "dmaap-mr-api" name: "message-router" port: *svc_port config: ssl: "redirect"
- Page 3: "Upgrades strimzi-operator from 0.28.0 to 0.36.1, Add podAntiAffinity to avoid deploying replica pods on the same node, We change strimzi replica count in helm override from 3 to 1 for single
node Kubernetes"- is added to "Montreal" release: https://gerrit.onap.org/r/c/oom/+/136590
- Page 5: "Does ONAP Plan to Deprecate DMaaP MR?"
- Yes, initially this was planned in London, but not implemented by all components (Policy, SDNC, DCAE,...)
- Plans:
- Policy:
Jira server ONAP Jira serverId 425b2b0a-557c-3c0c-b515-579789cceedb key POLICY-4402 - DCAE (some components) by DT
- AAI
- Policy:
- Still (in NewDehliNewDelhi) missing component support:
- Planned updates:
- AAI
- SO
- Policy
- some DCAE components
Fixes/Improvements
- Page 7: DMaaP mediator listens to MR topics
- To be checked
- Page 8: Move configurations to Values file
- Would gain more flexibility, but also much additional text in values.yaml
- Possibly only certain variable fields could be exposed
- Page 9/10: No reusable nonrtric-common chart / Common Templates
- good idea, also done in ONAP
- but adds dependency
- Page 11: Remove nested chart variables
- Or use "global.xxx" variables
- Page 12: YAML File Comparison
- use "helm/k8s recommended labels" → absolutely correct
- but allow to add own labels (e.g. "app", "version",...) in each chart or globally, as e.g. Istio, ArgoCD,... required special ones
- Page 13: Values File Changes
- Service definitions in "values.yaml" depends in ONAP much on the template definition (see https://git.onap.org/oom/tree/kubernetes/common/common/templates/_service.tpl)