Release Notes

F5 Service Proxy for Kubernetes (SPK) - v1.9.1

New Features and Improvements

SPK v1.9.1 is a bug fix release, and contains no new features.

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.

Bug Fixes

1408437-4 (Drivers)

Allocation now happens dynamically, adapting to conditions, so DPDK memory allocation works in a highly fragmented environment Now it succeeds even when two huge pages are not physically contiguous.

1468761 (Licensing)

The switch license no longer fails, even if triggered after the initial activation.

1494913-2 (fsm-protocols)

SPK with Custom Resource F5SPKIngressHTTP2 now handles “content-encoding: deflate” per RFC 7230.

1399773 (Ingress)

The Static Route CR deletion issue with finalizers is now resolved.

Known Issue

1505845 (Egress)

Ipv6 Egress Traffic is not Load Balancing across multiple TMMs.

Workaround

Downgrade to OCP 4.12

Software upgrades

Use these steps to upgrade the SPK software components:

_images/spk_warn.png Important: Steps 2 through 5 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 SPK Controller has been upgraded (step 3).
  2. 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.
  3. 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.
  4. Once the SPK Controller and TMM Pods are available, apply any updated CR configurations (step 1) using the oc apply -f <file> command.
  5. Follow the Upgrading DNS46 entries section of the F5SPKEgress CR guide to upgrade any entries created in versions 1.4.9 and earlier.
  6. 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.
  7. The dSSM Databases can be upgraded at anytime using the Upgrading dSSM guide.
  8. 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.
  9. The SPK can be upgraded from v1.7.x to v1.8.2 using the Upgrading SPK guide.

Next step

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