Page Comparison

...

• 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 Legacy
      server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key POLICY-4402

    • DCAE (some components) by DT
    • AAI
  • Still (in NewDehli) missing component support:
    Image RemovedImage Added

Fixes/Improvements

...