You can customize a CNF's infrastructure according to its unique requirements. Customizing the infrastructure requirements enables you to create a cluster, instantiate, and deploy the network functions without any manual user inputs.

Network functions from different vendors have their own unique set of infrastructure requirements. Defining these requirements in the network functions ensure that they are instantiated and deployed in a cluster without you having to log in to their master or worker nodes.

You can customize a network function's infrastructure requirements from the Network Functions > Catalogs tab. Click the network function that you want to customize and select the Source tab.

A new keyword called infra_requirements is introduced. Here, you can define the node, Containers as a Service (CaaS), and Platform as a Service (PaaS) components:
  1. Under node_components, define the Linux kernel type and kernel arguments for each worker node. You can also define any custom packages to be installed on your nodes here.
  2. Under caas_components, define the CaaS components such as CNIs to be installed on each worker node. A default version of Multus (version 1.16) is installed on all the worker nodes in the cluster.
  3. Under network, define the network name and the allocatable network resource name for the CaaS components.
After you define the components of infra_requirements in the CNF catalog, the cluster is customized according to the differences detected between the CNF catalog and the actual configuration present in the cluster during instantiation.