/
NF PaaS capability discussion:enhanced ingress for NF

NF PaaS capability discussion:enhanced ingress for NF

After completing cloud native OAM functions for CNF, a Ingress related function that can help CNF to expose its services for external access from outside the Kubernetes cluster may be the next Telco PaaS functionality.

Feature of Enhanced Ingress:

  • Ingress support to use L3/L4 rules to indicate traffice forward rules besides using L7 rules.

  • Ingress controller pod support to forward L3 traffic flows.

  • Ingress controller report its BGP route to router.

Features of NF services that use this enhanced ingress:

  • NF services that need external access is set in load balancer type when initiating.

  • NF services are aet to use the enhanced ingress controller pod as the load balancer provider.

Related content

2021-02-03 - ONAP: Cloud-Native (CNF) Taskforce - open discussion on current state and future plans
2021-02-03 - ONAP: Cloud-Native (CNF) Taskforce - open discussion on current state and future plans
More like this
2022-01-13 - ONAP: Orchestration of xNF Based 5G Service
2022-01-13 - ONAP: Orchestration of xNF Based 5G Service
More like this
4. LFN Projects Symphony (E2E Use Case and integration points)
4. LFN Projects Symphony (E2E Use Case and integration points)
More like this
FD.io Mini-Summit at LFN Developer Forum
FD.io Mini-Summit at LFN Developer Forum
More like this
2022 LFN Developer & Testing Forum January
2022 LFN Developer & Testing Forum January
More like this
Cloud Native Telecom Initiative (CNTi) - Depricated
Cloud Native Telecom Initiative (CNTi) - Depricated
More like this