The F5BigCneAddresslist Custom Resource (CR) is useful for defining larger, more complex lists of IP address that can then be referenced by Cloud-Native Network Functions (CNFs) protection and NAT CRs:

  • F5BigNatPolicy - Carrier-grade NAT (CG-NAT) using large-scale NAT (LSN) pools.
  • F5BigFwPolicy - Granulalar packet filtering based on access control list (ACL) policies.
  • F5BigDdosPolicy - Denial of Service (DoS/DDoS) event detection and mitigation.

This document guides you through creating a simple F5BigCneAddresslist.

_images/spk_info.png Note: The F5BigCnePortlist CR is useful for defining lists of service ports.


The CR spec parameters used to configure the Service Proxy TMM static routing table are:

Parameter Description
addresses The IPv4 or IPv6 addresses included in the address list: host 2002::10:10:10:1, subnet 2002::10:10:0:0/96, or range 2002::10:10:10:1-2002::10:10:10:20.


Ensure you have:


Use the following steps to install the F5BigCneAddresslist CR:

_images/spk_info.png Tip: Open a second shell to view the CNFs Event Logs while installing.

  1. Copy the example CR into a YAML file:

    apiVersion: "k8s.f5net.com/v1"
    kind: F5BigCneAddresslist
      name: "outbound-nat"
      namespace: "cnf-gateway"
      - "2002::192:168:10:1-2002::192:168:10:10"
      - "2002::10:10:10:0/112"
  2. Install the F5BigCneAddresslist CR:

    kubectl apply -f cnf-address-list.yaml

    In this example, the BIG-IP Controller logs indicate the F5BigCneAddresslist CR was added/updated:

    I0607 12:00:00.12345   1 event.go:282] Event(v1.ObjectReference{Kind:"F5AddressList", 
    F5AddressListProfile cnf-gateway/outbound-nat was added/updated


Provide feedback to improve this document by emailing cnfdocs@f5.com.