Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. 


External secure communication only via Ingress

ITEMDETAILS
Presentation

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyONAPARC-755

ARCCOM presentation

Recording MP4  


Audio Only   


Executive Summary - When ONAP is deployed using Service Mesh (default: Istio) all internal communication between pods is secured by sidecars. If components expose there services outside ONAP (e.g User interfaces, APIs,...) they have to use the Ingress Gateway provided (here Istio-Ingress). A communication via NodePorts is not supported anymore.

  • Helmcharts need to:

    • provide an Ingress resource (use existing helm template - common/templates/_ingress.tpl)
    • provide an Ingress configuration (as part of the values.yaml)
    • disable any Nodeport settings in services (if not use _service.tpl)

Business Impact - Supports a cloud-native application deployment.

Business Markets 

Funding/Financial Impacts 

Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. 


JIRA:
Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyREQ-1394
 

...