Release Notes¶
What’s New in SPK 2.0.0¶
Support for TMM Rolling Update¶
The TMM rolling update feature ensures seamless F5 Ingress updates by leveraging readinessGates (config and routing gates). It incrementally replaces TMM pods to maintain network traffic availability, with Kubernetes waiting for new pods before removing old ones. The upgrade process depends on maxUnavailable, maxSurge, and the number of TMM replicas.
For more information, see TMM Rolling Update.
Support for License Renewal¶
F5 has introduced a License Renewal feature to simplify the process of renewing your SPK license. After the LicenseExpiryDate, SPK continues processing traffic seamlessly but logs messages to renew. Contact the F5 sales team to renew your license. Once renewed, the F5 Licensing Server (TEEMs) updates the subscription details and sends them to the clusters once the telemetry reports are recieved, ensuring compliance and uninterrupted functionality.
For more information, see Renew Your License.
Simplified Voice-over-IP and Traditional Network Integration with F5SPKStatefulset CR¶
SPK supports the F5SPKStatefulset CR for interoperability between voice-over-IP (VoIP) networks and traditional telephone networks. This new signaling gateway capability enables seamless communication across network technologies by facilitating integration through circuit switching and SS7 protocols.
For more information, see F5SPKStatefulset.
Support for Outbound Diameter Flow with F5SPKEgressDiameter CR¶
SPK supports the F5SPKEgressDiameter CR to enhance outbound Diameter flows to external peers. It also provides options to tune TCP or SCTP connection processing and to monitor the health of service object endpoints.
For more information, see F5SPKEgressDiameter.
Support for Multiple External Gateways with AdminPolicyBasedExternalRoute CR¶
SPK supports the AdminPolicyBasedExternalRoute CR to enhance the Multiple External Gateway (MEG) feature. This enhancement allows admin users to configure OpenShift to utilize the MEG feature. This CR provides control over the routing of egress traffic from specific namespaces through the Traffic Management Microkernel (TMM) and plays a crucial role in managing external traffic across multiple gateways when using SPK.
For more information, see AdminPolicyBasedExternalRoute.
Limitations¶
Jumbo Frames - The maximum transmission unit (MTU) must be the same size on both ingress and egress interfaces. Packets over 9000 bytes are dropped.
Fixes and Known Issue¶
Refer to Fixes and Known Issues section to known about fixes and known issues for this SPK release.
Software upgrades¶
Upgrade the SPK Software Components¶
Use these steps to upgrade the SPK software components:
Important: Steps 2 through 5 should be performed together, and during a planned maintenance window.
Review the What’s New in SPK 2.0.0 section above, and integrate any updates into the existing configuration. Do not apply Custom Resource (CR) updates until after the SPK Controller has been upgraded, see Upgrade SPK from v1.7.14 to v2.0.0.
Follow Install the CRDs in the SPK Software guide to upgrade the CRDs. Be aware that newly applied CRDs will replace existing CRDs of the same name.
Uninstall the previous version SPK Controller, and follow the Installation procedure in the SPK Controller guide to upgrade the Controller and TMM Pods. Upgrades have not yet been tested using Helm Upgrade.
Once the SPK Controller and TMM Pods are available, apply any updated CR configurations (step 1) using the
oc apply -f <file>command.Follow the Upgrading DNS46 entries section of the F5SPKEgress CR guide to upgrade any entries created in versions 1.4.9 and earlier.
Uninstall the previous version SPK CWC, and for 1.7.0 and later installations RabbitMQ, and follow the Install RabbitMQ and Install CWC procedures in the SPK CWC guide to upgrade the Pods. Upgrades have not yet been tested using Helm Upgrade.
The dSSM Databases can be upgraded at anytime using the Upgrading dSSM guide.
The Fluentd Logging collector can be upgraded anytime using Helm Upgrade. Review Extract the Images in the SPK Software guide for the new Fluentd Helm chart location.
Next step¶
Continue to the Cluster Requirements guide to ensure the OpenShift cluster has the required software components.