Release Notes

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

New Features and Improvements

  • The SPK CWC (Cluster Wide Controller) introduces F5’s flexible consumption software licensing, billing monthly only for the software features used.
  • The OTEL Collectors (Early Access) gather detailed SPK Pod health statistics for third-party data collection and visualization software such as Prometheus and Grafana. Important: The OTEL Collectors require new Secrets, review SPK Secrets for the installation steps.
  • The F5SPKEgress CR now references the F5SPKDnscache CR by concatenating the CR’s metadata.namespace and metadata.name parameters with a hyphen (-) character. For example, dnsCacheName: ingress-dnscache.
  • The tmm.bfdToOvn parameter enhances OVN Kubernetes to quickly detect loss of connectivity between TMMs and OVN gateway nodes. This parameter should be enabled when TMM is used as an egress gateway. Refer to the SPK Controller overview.

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. 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

1092013 (TMM Routing)

The IMI shell (imish) is now accessible after a TMM container restart.

Known Issues

1105561 (TMM)

Bidirectional Forwarding Detection (BFD) sessions with OVN-Kubernetes may fail to established after deleting and reapplying the internal F5SPKVlan CR.

Workaround:

Scale the TMM Pod down, ensure the Pod terminates (is no longer running), and then scale the Pod back up.

1. oc scale deploy/f5-tmm --replicas 0
2. oc get pods
3. oc scale deploy/f5-tmm --replicas 1

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, ensure the Pod terminates (is no longer running), and then scale the Pod back up.

1. oc scale deploy/f5-tmm --replicas 0
2. oc get pods 
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.