Download the SF Binary

To enable datapath on BF3 DPU which is SF-based (instead of VF-based) a custom CNI plugin is automatically installed as part of TMM daemonset. This is referred by the network attachment definitions so that the plugin can be invoked and perform its task in enabling SFs for the TMM pod.

  1. Login to Helm Registry, see Helm Registry Login section in Artifacts via F5 Artifact Registry (FAR).

  2. Pull the tarball.

    helm pull oci://repo.f5.com/utils/f5-eowyn  --version 2.0.0-LA.1-0.0.11

    Sample Output:

    Pulled: repo.f5.com/utils/f5-eowyn:2.0.0-LA.1-0.0.11
Digest: sha256:ce53f44b832d7a738a22f0e8f9902eac54a2507e86a9debfd090c5ad110631ba

  3. Verify that the downloaded tarbal available.

    ls -ltr f5-eowyn-2.0.0-LA.1-0.0.11.tgz

    Sample Output:

    -rw-r--r-- 1 root root 1084611 Dec  5 11:19 f5-eowyn-2.0.0-LA.1-0.0.11.tgz

  4. Untar the downloaded tarball.

    tar -xzvf f5-eowyn-2.0.0-LA.1-0.0.11.tgz

    Sample Output:

    f5-eowyn/
f5-eowyn/Chart.yaml
f5-eowyn/sf

  5. Verify that the untar is successfull and the sf binary is available:

    ls f5-eowyn

    Sample Output:

    Chart.yaml  sf

  6. Make sf executable. Run:

    chmod +x sf

  7. Move the sf to the DPU’s path /opt/cni/bin.

    /opt/cni/bin/sf

    Sample Output:

    version: v0.0.11 (clean, released) commit: df4089251cd8a5a80cd9ee97942ac4f6bf85ad99 build date: 2024-12-04T08:30:35+00:00
CNI protocol versions supported: 0.1.0, 0.2.0, 0.3.0, 0.3.1, 0.4.0, 1.0.0, 1.1.0