Release Notes

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

New Features and Improvements

This release contains bug fixes only.

Software upgrades

Use these following 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 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 updated CR configurations using the oc apply -f <file> command.
  5. Follow the Upgrading DNS46 entries section of the F5SPKEgress CR guide to upgrade entries created in versions 1.4.9 and earlier.
  6. The dSSM Databases can be upgraded at anytime using the Upgrading dSSM guide.
  7. 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.

Limitations

  • Jumbo Frames - The maximum transmission unit (MTU) must be the same size on both ingress and egress interfaces. Packets over 8000 bytes are dropped.

Bug Fixes

1091937 (Controller)

When an F5SPKSnatpool CR is installed and the TMM container restarts, TMM now receives the correct SNAT Pool IP addresses.

1090249 (Controller)

When one of the application traffic SPK CRs is installed and the TMM container restarts, TMM now receives the application traffic configuration.

1089509 (Controller)

When an F5SPKVlan CR is installed and the TMM container restarts, TMM now receives the network interface configuration.

Known Issues

1092013 (TMM Routing)

The IMI shell (imish) may not be accessible after a TMM container restart.

Workaround:

Log in to the f5-tmm-routing container and restart the imi process.

1. oc exec -it deploy/f5-tmm -c f5-tmm-routing -- bash
2. ps ax | grep imi
3. kill -9 482

1091997 (TMM)

In dual-stack configurations, application traffic SPK CRs remain in the TMM configuration, even when the watched application is scaled to 0.

Workaround:

Scale the TMM Pod down/up.

1. oc scale deploy/f5-tmm --replicas 0
2. Wait for f5-tmm to terminate
3. oc scale deploy/f5-tmm --replicas 1

Next step

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