docs: adjust docs for 25.7.1 and add release notes

* docs: adjust docs for 25.7.1 and add release notes

this commit adds the docs for 25.7.1 release and add relevant release
notes

Signed-off-by: Vasilis Remmas <[email protected]>

Based on release-v25.7@c2430c728b0d38df43a8ad38120c4faa613bddf0

Author: vasrem

docs/public/developer-guides/api/dpudeployment.md

@@ -303,13 +303,13 @@ spec:
         matchLabels:
           datacenter.nvidia.com/rack: "b-100"
       dpuSelector:
-        pciAddr: "0000:0e:00.0"
+        provisioning.dpu.nvidia.com/dpudevice-pciAddress: "0000:0e:00.0"
     - nameSuffix: "dpuset2"
       nodeSelector:
         matchLabels:
           datacenter.nvidia.com/rack: "b-101"
       dpuSelector:
-        pciAddr: "0000:1a:00.0"
+        provisioning.dpu.nvidia.com/dpudevice-pciAddress: "0000:1a:00.0"
   # services reflects the `DPUServices` that should be deployed on those DPUs. The key of this map is the service name
   # and the value is referencing the respective `DPUServiceTemplate` and `DPUServiceConfiguration` for that each service.
   services:
@@ -382,13 +382,13 @@ spec:
         matchLabels:
           datacenter.nvidia.com/rack: "b-100"
       dpuSelector:
-        pciAddr: "0000:0e:00.0"
+        provisioning.dpu.nvidia.com/dpudevice-pciAddress: "0000:0e:00.0"
     - nameSuffix: "dpuset2"
       nodeSelector:
         matchLabels:
           datacenter.nvidia.com/rack: "b-101"
       dpuSelector:
-        pciAddr: "0000:1a:00.0"
+        provisioning.dpu.nvidia.com/dpudevice-pciAddress: "0000:1a:00.0"
     nodeEffect:
       taint:
         key: "dpu"
@@ -411,10 +411,12 @@ The following fields are available in the `spec.dpus`:
   by the `DPUDeployment`.
     * `nameSuffix`: A suffix to be added to the `DPUSet` name. This is a required
       field, as the `DPUSet` name must be unique and identifiable.
-    * `nodeSelector`: The node selector to be used to select the nodes to which the
-      DPUs are attached.
-    * `dpuSelector`: The selector to be used to select the DPUs that are to be targeted.
-      In this example, the DPUs are selected based on their PCI address.
+    * `nodeSelector`: The selector of the DPUNodes to which the DPUs are attached
+      to. See more in [DPU Selection](./dpuset.md#dpu-selection). Note that this
+      field maps to the DPUSet field `dpuNodeSelector`.
+    * `dpuSelector`: The selector of the DPUDevices that are to be targeted. In
+      this example, the DPUs are selected based on their PCI address. See more in
+      [DPU Selection](./dpuset.md#dpu-selection).
     * `dpuAnnotations`: The annotation to be applied on the DPU objects that are
       created by the `DPUDeployment`.
 * `nodeEffect`: The effect to be applied on the nodes to which the DPUs are attached.

docs/public/developer-guides/api/dpuset.md

@@ -113,6 +113,66 @@ spec:
         effect: NoSchedule
 ```
 
+## DPU Selection
+
+The DPUSet provides two complementary mechanisms for selecting which DPUs should be managed: `dpuNodeSelector` and
+`dpuSelector`.
+
+### dpuNodeSelector
+
+The `dpuNodeSelector` field is used to select DPUNodes based on their labels. It uses the 
+standard Kubernetes LabelSelector format, which supports both `matchLabels` and `matchExpressions`.
+
+For example, to select nodes with a specific label:
+
+```yaml
+spec:
+  dpuNodeSelector:
+    matchLabels:
+      feature.node.kubernetes.io/dpu-enabled: "true"
+```
+
+Or using match expressions for more complex selection:
+
+```yaml
+spec:
+  dpuNodeSelector:
+    matchExpressions:
+      - key: environment
+        operator: In
+        values:
+          - production
+          - staging
+```
+
+### dpuSelector
+
+The `dpuSelector` field is used to further filter DPUDevices based on their labels. This is applied after the
+`dpuNodeSelector` and allows you to select specific DPUDevices on the selected DPUNodes.
+
+The `dpuSelector` uses a simple map of label key-value pairs, where all specified labels must match (AND logic).
+
+For example, to select only specific DPU models or configurations:
+
+```yaml
+spec:
+  dpuNodeSelector:
+    matchLabels:
+      feature.node.kubernetes.io/dpu-enabled: "true"
+  dpuSelector:
+    provisioning.dpu.nvidia.com/dpudevice-pciAddress: "0000:1a:00.0"
+```
+
+In Host Trusted model, the automatically created DPUDevice objects have the following labels:
+
+- `provisioning.dpu.nvidia.com/dpudevice-num-of-pfs`: The number of PFs on the DPU device
+- `provisioning.dpu.nvidia.com/dpudevice-pciAddress`: The PCI address of the DPU device
+- `provisioning.dpu.nvidia.com/dpudevice-pf0-name`: The name of PF0 on the DPU device
+- `provisioning.dpu.nvidia.com/dpunode-name`: The name of the DPUNode the DPU is part of
+
+### Selection Flow
+
+
 ## Host Power-cycle in DPU provisioning
 
 If the version of running BFB is lower than 2.7 before DPU provisioning, the BlueField firmware upgrades and mlxconfig

docs/public/getting-started/dpf-host-trusted.md

@@ -64,13 +64,13 @@ helm repo update
 Deploy the DPF Operator to your Kubernetes cluster using Helm:
 
 ```bash
-helm upgrade --install -n dpf-operator-system dpf-operator dpf-repository/dpf-operator --version=v25.7.0
+helm upgrade --install -n dpf-operator-system dpf-operator dpf-repository/dpf-operator --version=v25.7.1
 ```
 
 The command above does the following:
 
 * Creates the `dpf-operator-system` namespace if it doesn't exist
-* Installs the DPF Operator version v25.7.0 from the NVIDIA repository
+* Installs the DPF Operator version v25.7.1 from the NVIDIA repository
 
 ### 3. Verify the Installation
 

docs/public/getting-started/dpf-zero-trust.md

@@ -64,13 +64,13 @@ helm repo update
 Deploy the DPF Operator to your Kubernetes cluster using Helm:
 
 ```bash
-helm upgrade --install -n dpf-operator-system dpf-operator dpf-repository/dpf-operator --version=v25.7.0
+helm upgrade --install -n dpf-operator-system dpf-operator dpf-repository/dpf-operator --version=v25.7.1
 ```
 
 The command above does the following:
 
 * Creates the `dpf-operator-system` namespace if it doesn't exist
-* Installs the DPF Operator version v25.7.0 from the NVIDIA repository
+* Installs the DPF Operator version v25.7.1 from the NVIDIA repository
 * Configures the operator to manage DPU resources across your cluster
 
 ### 3. Verify the Installation

docs/public/getting-started/helm-prerequisites.md

@@ -56,7 +56,7 @@ The helmfiles are located at `deploy/helmfiles/` in the [DPF repository].
 
 This approach ensures consistent deployment across different environments and simplifies the installation process.
 
-> [!NOTE] You have to install the `local-path-provisioner` manually. The current helmfile for the release v25.7.0 does not
+> [!NOTE] You have to install the `local-path-provisioner` manually. The current helmfile for the release v25.7.1 does not
 > include it, but it is required for the Kamaji etcd storage.
 
 You can install the `local-path-provisioner` it with the following command:

docs/public/release-notes/README.md

@@ -6,6 +6,7 @@ title: "Release Notes"
 
 This section contains release notes for the DOCA Platform Framework (DPF), documenting new features, improvements, and bug fixes for each version.
 
+* [v25.7.1](./v25.7.1.md)
 * [v25.7.0](./v25.7.0.md)
 * [v25.4.0](./v25.4.0.md)
 * [v25.1.1](./v25.1.1.md)

docs/public/release-notes/v25.7.1.md

@@ -0,0 +1,27 @@
+---
+title: "DOCA Platform Framework v25.7.1"
+---
+
+This is a patch release on top of the 25.7.0 release of the DOCA Platform Framework (DPF).
+It includes bug fixes and improvements to enhance the provisioning and orchestration of
+NVIDIA BlueField DPUs in Kubernetes environments.
+
+The [release notes for 25.7.0](./v25.7.0.md) still apply for this release and information
+presented in this documentation is an amendment to the previous release notes.
+
+This release contains artifacts only for the core DPF components and doesn't include VPC,
+Storage and OVN Kubernetes related artifacts.
+
+### Features
+
+* **Support provisioning a single DPU in nodes that have more than one DPU**: This feature
+  enables customers to select which DPU DPF should provision and run services on in systems
+  that have more than 1 DPU. It's still not supported to provision more than 1 DPU per node.
+
+### Fixed Issues from previous release
+
+* **[HBN DPUService] Pod stuck in CrashLoopBackOff due to hbn-sidecar failing**
+    * Occasionally, on creation of the HBN DPUService Pod, it could happen that the hbn-sidecar
+      container would fail to run `ovs-ofctl add-flow` with arguments that contain `in_port=-1`.
+      In this release, we introduced a patch that helps reduce the probability of this happening.
+    * Internal Ref #4618866

docs/public/user-guides/host-trusted/prerequisites/system.md

@@ -29,7 +29,7 @@ Each worker machine:
 * x86_64 architecture
 * 16 GB RAM
 * 8 CPUs
-* Exactly one DPU
+* Any number of DPUs **but only one can be provisioned**
 
 #### DPUs
 

docs/public/user-guides/host-trusted/use-cases/hbn-ovnk/README.md

@@ -135,7 +135,7 @@ export SERVICE_CIDR=10.233.0.0/18
 export REGISTRY=https://helm.ngc.nvidia.com/nvidia/doca
 
 ## The DPF TAG is the version of the DPF components which will be deployed in this guide.
-export TAG=v25.7.0
+export TAG=v25.7.1
 
 ## URL to the BFB used in the `bfb.yaml` and linked by the DPUSet.
 export BFB_URL="https://content.mellanox.com/BlueField/BFBs/Ubuntu22.04/bf-bundle-3.1.0-76_25.07_ubuntu-22.04_prod.bfb"
@@ -162,7 +162,7 @@ kubectl create ns ovn-kubernetes
 
 Install the OVN Kubernetes CNI components from the helm chart. A number of [environment variables](#0-required-variables) must be set before running this command.
 ```shell
-envsubst < manifests/01-cni-installation/helm-values/ovn-kubernetes.yml | helm upgrade --install -n ovn-kubernetes ovn-kubernetes ${OVN_KUBERNETES_REPO_URL}/ovn-kubernetes-chart --version $TAG --values -
+envsubst < manifests/01-cni-installation/helm-values/ovn-kubernetes.yml | helm upgrade --install -n ovn-kubernetes ovn-kubernetes ${OVN_KUBERNETES_REPO_URL}/ovn-kubernetes-chart --version v25.7.0 --values -
 ```
 
 <details markdown="1"><summary>OVN-Kubernetes Helm values</summary>
@@ -432,7 +432,7 @@ operator:
 The OVN Kubernetes resource injection webhook injected each pod scheduled to a worker node with a request for a VF and a Network Attachment Definition. This webhook is part of the same helm chart as the other components of the OVN Kubernetes CNI. Here it is installed by adjusting the existing helm installation to add the webhook component to the installation. 
 
 ```shell
-envsubst < manifests/04-enable-accelerated-cni/helm-values/ovn-kubernetes.yml | helm upgrade --install -n ovn-kubernetes ovn-kubernetes-resource-injector ${OVN_KUBERNETES_REPO_URL}/ovn-kubernetes-chart --version $TAG --values -
+envsubst < manifests/04-enable-accelerated-cni/helm-values/ovn-kubernetes.yml | helm upgrade --install -n ovn-kubernetes ovn-kubernetes-resource-injector ${OVN_KUBERNETES_REPO_URL}/ovn-kubernetes-chart --version v25.7.0 --values -
 ```
 
 <details markdown="1"><summary>OVN Kubernetes Resource Injector Helm values</summary>
@@ -525,6 +525,11 @@ that should run on a set of DPUs.
 
 #### Create the DPUDeployment, DPUServiceConfig, DPUServiceTemplate and other necessary objects
 
+> [!WARNING]
+> In case more than 1 DPU exists per node, the relevant selector should be applied in the DPUDeployment
+> to select the appropriate DPU. See [DPUDeployment - DPUs Configuration](../../../../developer-guides/api/dpudeployment.md#dpus-configuration)
+> to understand more about the selectors.
+
 A number of [environment variables](#0-required-variables) must be set before running this command.
 ```shell
 cat manifests/05-dpudeployment-installation/*.yaml | envsubst | kubectl apply -f - 
@@ -566,6 +571,8 @@ spec:
       nodeSelector:
         matchLabels:
           feature.node.kubernetes.io/dpu-enabled: "true"
+      dpuSelector:
+        provisioning.dpu.nvidia.com/dpudevice-pf0-name: $DPU_P0
   services:
     ovn:
       serviceTemplate: ovn
@@ -647,7 +654,7 @@ spec:
     source:
       repoURL: $OVN_KUBERNETES_REPO_URL
       chart: ovn-kubernetes-chart
-      version: $TAG
+      version: v25.7.0
     values:
       commonManifests:
         enabled: true

docs/public/user-guides/host-trusted/use-cases/hbn-ovnk/manifests/00-env-vars/envvars.env

@@ -50,7 +50,7 @@ export SERVICE_CIDR=10.233.0.0/18
 export REGISTRY=https://helm.ngc.nvidia.com/nvidia/doca
 
 ## The DPF TAG is the version of the DPF components which will be deployed in this guide.
-export TAG=v25.7.0
+export TAG=v25.7.1
 
 ## URL to the BFB used in the `bfb.yaml` and linked by the DPUSet.
 export BFB_URL="https://content.mellanox.com/BlueField/BFBs/Ubuntu22.04/bf-bundle-3.1.0-76_25.07_ubuntu-22.04_prod.bfb"