Release Notes

F5 Cloud-Native Network Functions (CNF) - 1.0.0 Limited Availability (LA)

New Features and Improvements

  • The F5BigDnsApp CR’s dns64Mode converts IPv4 DNS responses into IPv6 format.

    Reference CNFs NAT64 and the dns64Mode section of the F5BigDnsApp Reference.

  • CNFs CRs can now be managed using Kubernetes shortNames.

    Reference the CRD shortName section in any of the CNFs CRs.

  • The F5BigDnsApp CR’s udp parameter has changed to udpSettings.

    Reference the spec section of the F5BigDnsApp Reference.

Bug Fixes

1076469 (TMM)

The Traffic Management Microkernel (TMM) is now able to process Point-to-Point Tunneling Protocol (PPTP) traffic using the F5BigAlgPptp Custom Resource (CR).

Known Issues

1115593 (TMM)

The TMM Proxy Pod is unable to process large files (~1GB) using the F5BigAlgPptp CR when the maximum transmission unit (MTU) is greater than 1450 bytes.

Workaround: Set the PPTP interface MTU to 1450 bytes or less.

1112949 (Controller)

The F5BigNatPolicy configuration may appear missing after restarting the TMM Proxy Pod causing subscriber NAT connections to fail.

Workaround: Delete the AFM Pod to spawn a new Pod, and restore communication between the BIG-IP Controller and PCCD PODs.

kubectl delete pod <afm-pod-name> -n <namespace>

1063321 (TMM)

When multiple TMMs are running in a single Namespace, the IP addresses allocated by the F5BigNatPolicy are not reclaimed and reallocated after scaling the TMM deployment down and back up. Client connections may fail due to NAT IP address exhaustion.

Workaround: Delete and reinstall the F5BigNatPolicy CR.

1053293 (Controller)

TMM Proxy Pods may fail to receive a self-IP address when the F5BigNetVlan CR allocates the same number self-IPs as running TMM Proxy Pods.

Workaround: Configure the F5BigNetVlan to allocate twice the number of self-IP addresses as running TMM Proxy Pods.

Software upgrades

Use these steps to upgrade the CNFs software components:

_images/spk_warn.png Important: Steps 2 through 4 should be performed together, and during a planned maintenance window.

  1. Review the New Features and Improvements section above, and integrate any updates into the existing configuration. Do not apply Custom Resource (CR) updates until after the BIG-IP Controller has been upgraded.
  2. Follow Install the CRDs in the CNFs Software guide to upgrade the CRDs. Be aware that newly applied CRDs will replace existing CRDs of the same name.
  3. Uninstall the previous version BIG-IP Controller, and follow the Installation procedure in the BIG-IP Controller guide to upgrade the Controller and TMM Proxy Pods. Upgrades have not yet been tested using Helm Upgrade.
  4. Once the BIG-IP Controller and TMM Proxy Pods are available, apply any updated CR configurations (step 1) using the kubectl apply -f <file> command.
  5. The dSSM Databases can be upgraded at anytime using the Upgrading dSSM guide.
  6. The Fluentd Logging collector can be upgraded anytime using Helm Upgrade. Review Extract the Images in the CNF Software guide for the new Fluentd Helm chart location.

Next step

Continue to the Cluster Requirements guide to ensure the cluster has the required software components.