Release Notes¶

What’s New in SPK 2.2¶

Supporting high-performing NIC drivers¶

You can now use Mellanox ConnectX-7, Broadcom BCM57414 NetXtreme-E 10Gb/25Gb and Broadcom BCM57508 NetXtreme-E 10Gb/25Gb/40Gb/50Gb/100Gb/200Gb NIC drivers with SPK software from this release. For more information, see Supported NICs

Ensure seamless and secure communication with external networks¶

The Kubernetes resource, F5SPKEgressSIP, can now be installed using Helm or FLO. This feature allows SIP applications to communicate with external networks. For more information, see F5SPKEgressSIP

Dynamically manage log levels via REST API and ConfigMap watching¶

This new feature allows runtime log level control without pod restarts. CWC now exposes a REST API to adjust log levels per pod. Requests update a pod-specific ConfigMap, which propagates via minlevel.yaml; the F5 logging library monitors this file and applies the new level automatically. For more information, see Dynamic Log Level and API Documentation

Automated orphaned log folder cleanup¶

Added Folder Cleaner, an optional feature that automatically removes orphaned log directories to prevent storage exhaustion. Cleanup runs as a scheduled job (CronJob) inside the container. For more information, see Fluend Logging

End-to-end security for sensitive configuration information¶

The feature introduces Kubernetes native Secret support to manage sensitive data (like certificates and keys) securely in Custom Resources (CRs). You can create a Kubernetes secret and reference the Secret using secretRef (name, namespace, and key) instead of embedding sensitive data in plain text. Secrets can be dynamically edited or renewed via cert-manager without the need to re-apply the CR. The cne-controller securely fetches the Secret with proper RBAC, watches for updates, and notifies consumers. Sensitive data is transmitted securely using mTLS for end-to-end security. For more information, seeF5SPKEgressHTTP2 and F5SPKIngressHTTP2

Enhancements¶

Added support for 1 GB huge pages¶

You can now configure the huge page size to 1Gi using the new tmm.hugepages.preferredhugepagesize parameter while defining the TMM resources. For more information, see Manual CPU Allocation

Cancelling QKView Requests by ID¶

Cancel a running QKView via API; on cancellation, the system stops collection and generates a QKView that includes only data gathered before the cancel request. For more information, see QKView and API Documentation

Configuring per-table aggregation¶

You can now use Aggregation mode to control metrics for a table. For each table, you can choose the Aggregation mode options (Aggregated, Semi Aggregated, or Diagnostic) and set an export interval. The operator enforces these settings via Jobs from the f5-observer-operator-config ConfigMap. For more information, see Aggregation Mode and Metric Tables

Fixes and Known Issues¶

Refer to Fixes and Known Issues section to known about fixes and known issues for this SPK release.

Software upgrades¶

Refer to Upgrade Steps

Next step¶

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