The Integration documentation section is organized linearly; each document representing the next step in the Cloud-Native Network Functions (CNFs) integration process. The CNFs integration process relies heavily on the Helm package manager to install each of the CNFs software components.
This document provides a brief description of each integration step, and the command line interface (CLI) tools required to perform the integration tasks. A careful review of this document ensures a positive experience.
Note: You can click Next at the bottom of each page, or scroll through the CNFs PDF to follow the integration process.
Install the CLI tools listed below on your Linux based workstation:
- Helm CLI - Manages the CNFs Pod installations.
- OpenSSL toolkit - Creates SSL certificates to secure Pod communication.
- Podman - Tags and pushes images to a local registry.
Integrating the CNFs software images involves seven required steps, and three optional steps:
- CNFs Software - Extract and upload the CRDs and software images to a local container registry.
- CNFs Cert Manager - Automatically Secure communication between the CNFs Pods, and regularly rotate secure secrets.
- CNFs RBAC - Optional: Secure access to the Kubernetes API when installing CNFs.
- Fluentd Logging - Centralize logging data sent from each of the CNF Pods.
- OTEL Collectors - Optional: Collect and view statistics from the CNFs Pods.
- dSSM Database - Optional: Store session-state data for the AFM and TMM Pods.
- CNFs CWC - Install the Cluster Wide Controller to enable gathering CNFs software telemetry.
- CNFs Licensing - License the cluster to enable flexible consumption software use.
- BIG-IP Controller - Process CNFs Custom Resources to configure the CNFs Pods.
- CNFs CRs - Configure a Custom Resource (CR) to begin processing application traffic.
Continue to the CNFs Software guide to extract and install the CNFs software images and CRDs.
Provide feedback to improve this document by emailing firstname.lastname@example.org.