RDG for DPF Zero Trust (DPF-ZT) with DOCA Telemetry Service(DTS) and Blueman services

Created on Jan 18, 2026

Scope

This Reference Deployment Guide (RDG) provides comprehensive instructions for deploying the NVIDIA DOCA Platform Framework (DPF) on high-performance, bare-metal infrastructure in Zero-Trust mode. The guide focuses on setting up the DOCA Telemetry Service (DTS) and the BlueMan Service on NVIDIA® BlueField®-3 DPUs, enabling a unified interface for accessing essential DPU information, health status, and telemetry metrics.

The guide is intended for experienced system administrators, systems engineers, and solution architects who build highly secure bare-metal environments with Host-Based Networking enabled using NVIDIA BlueField DPUs for acceleration, isolation, and infrastructure offload.

This document is an extension of the RDG for DPF Zero Trust (DPF-ZT) - NVIDIA Docs (referred to as the Baseline RDG ). It details the additional steps and modifications required to deploy the DTS and BlueMan Services into the Baseline RDG environment.

Abbreviations and Acronyms

Introduction

The NVIDIA BlueField-3 Data Processing Unit (DPU) is a 400 Gb/s infrastructure compute platform designed for line-rate processing of software-defined networking, storage, and cybersecurity workloads. It combines powerful compute resources, high-speed networking, and advanced programmability to deliver hardware-accelerated, software-defined solutions for modern data centers.

NVIDIA DOCA unleashes the full potential of the BlueField platform by enabling rapid development of applications and services that offload, accelerate, and isolate data center workloads.

DOCA Telemetry Service (DTS) collects data from built-in providers (data providers such as sysfs , ethtool and tc , and aggregation providers such as fluent_aggr and prometheus_aggr ), and from external telemetry applications.

DOCA BlueMan runs in the DPU as a standalone web dashboard and consolidates all the basic information, health, and telemetry counters into a single interface.

All the information that BlueMan provides is gathered from the DOCA Telemetry Service (DTS).

However, deploying and managing DPUs, especially at scale, presents operational challenges. Without a robust provisioning and orchestration system, tasks such as lifecycle management, service deployment, and network configuration for service function chaining (SFC) can quickly become complex and error prone. This is where the DOCA Platform Framework (DPF) comes into play.

DPF automates the full DPU lifecycle, and simplifies advanced network configurations. With DPF, services can be deployed seamlessly, allowing for efficient offloading and intelligent routing of traffic through the DPU data plane.

By leveraging DPF, users can scale and automate DPU management across Bare Metal, Virtual, and Kubernetes customer environments - optimizing performance while simplifying operations.

DPF supports multiple deployment models. This guide focuses on the Zero Trust bare-metal deployment model. In this scenario:

• The DPU is managed through its Baseboard Management Controller (BMC)
• All management traffic occurs over the DPU's out-of-band (OOB) network
• The host is considered as an untrusted entity towards the data center network. The DPU acts as a barrier between the host and the network.
• The host sees the DPU as a standard NIC, with no access to the internal DPU management plane (Zero Trust Mode)

This Reference Deployment Guide (RDG) provides a step-by-step example for installing DPF in Zero-Trust mode. It also includes practical demonstrations of performance optimization, validated using standard RDMA and TCP workloads.

As part of the reference implementation, open-source components outside the scope of DPF (e.g., MAAS, pfSense, Kubespray) are used to simulate a realistic customer deployment environment. The guide includes the full end-to-end deployment process, including:

• Infrastructure provisioning
• DPF deployment
• DPU provisioning (redfish)
• Service configuration and deployment
• Service chaining.

This document is an extension of the RDG for DPF Zero Trust (DPF-ZT) - NVIDIA Docs (referred to as the Baseline RDG ). It details the additional steps and modifications required to deploy the DTS and BlueMan Services into the Baseline RDG environment.

References

• NVIDIA BlueField DPU
• NVIDIA DOCA
• NVIDIA DPF Release Notes
• NVIDIA DPF GitHub Repository
• NVIDIA DPF System Overview
• NVIDIA Ethernet Switching
• NVIDIA Cumulus Linux
• What is K8s?
• Kubespray

Solution Architecture

Key Components and Technologies

• NVIDIA BlueField® Data Processing Unit (DPU)

  The NVIDIA® BlueField® data processing unit (DPU) ignites unprecedented innovation for modern data centers and supercomputing clusters. With its robust compute power and integrated software-defined hardware accelerators for networking, storage, and security, BlueField creates a secure and accelerated infrastructure for any workload in any environment, ushering in a new era of accelerated computing and AI.
  

• NVIDIA DOCA Software Framework

  NVIDIA DOCA™ unlocks the potential of the NVIDIA® BlueField® networking platform. By harnessing the power of BlueField DPUs and SuperNICs, DOCA enables the rapid creation of applications and services that offload, accelerate, and isolate data center workloads. It lets developers create software-defined, cloud-native, DPU- and SuperNIC-accelerated services with zero-trust protection, addressing the performance and security demands of modern data centers.
  

• NVIDIA ConnectX SmartNICs

  10/25/40/50/100/200 and 400G Ethernet Network Adapters

  The industry-leading NVIDIA® ConnectX® family of smart network interface cards (SmartNICs) offer advanced hardware offloads and accelerations.

  NVIDIA Ethernet adapters enable the highest ROI and lowest Total Cost of Ownership for hyperscale, public and private clouds, storage, machine learning, AI, big data, and telco platforms.
  

• NVIDIA LinkX Cables

  The NVIDIA® LinkX® product family of cables and transceivers provides the industry’s most complete line of 10, 25, 40, 50, 100, 200, and 400GbE in Ethernet and 100, 200 and 400Gb/s InfiniBand products for Cloud, HPC, hyperscale, Enterprise, telco, storage and artificial intelligence, data center applications.
  

• NVIDIA Spectrum Ethernet Switches

  Flexible form-factors with 16 to 128 physical ports, supporting 1GbE through 400GbE speeds.

  Based on a ground-breaking silicon technology optimized for performance and scalability, NVIDIA Spectrum switches are ideal for building high-performance, cost-effective, and efficient Cloud Data Center Networks, Ethernet Storage Fabric, and Deep Learning Interconnects.

  NVIDIA combines the benefits of NVIDIA Spectrum^™ switches, based on an industry-leading application-specific integrated circuit (ASIC) technology, with a wide variety of modern network operating system choices, including NVIDIA Cumulus^® Linux , SONiC and NVIDIA Onyx^®.

• NVIDIA Cumulus Linux

  NVIDIA® Cumulus® Linux is the industry's most innovative open network operating system that allows you to automate, customize, and scale your data center network like no other.
  

• Kubernetes

  Kubernetes is an open-source container orchestration platform for deployment automation, scaling, and management of containerized applications.
  

• Kubespray

  Kubespray is a composition of Ansible playbooks, inventory, provisioning tools, and domain knowledge for generic OS/Kubernetes clusters configuration management tasks and provides:

  • A highly available cluster
  • Composable attributes
  • Support for most popular Linux distributions

Solution Design

Solution Logical Design

The logical design includes the following components:

• 1 x Hypervisor node (KVM-based) with ConnectX-7:

  • 1 x Firewall VM
  • 1 x Jump Node VM
  • 1 x MaaS VM
  • 3 x K8s Master VMs running all K8s management components
• 1 x Worker nodes (PCI Gen5), each with a 1 x BlueField-3 NIC
• Single High-Speed (HS) switch
• 1 Gb Host Management network

Firewall Design

The pfSense firewall in this solution serves a dual purpose:

• Firewall—provides an isolated environment for the DPF system, ensuring secure operations
• Router—enables Internet access for the management network

Port-forwarding rules for SSH and RDP are configured on the firewall to route traffic to the jump node’s IP address in the host management network. From the jump node, administrators can manage and access various devices in the setup, as well as handle the deployment of the Kubernetes (K8s) cluster and DPF components.
The following diagram illustrates the firewall design used in this solution:

Software Stack Components

Bill of Materials

Deployment and Configuration

Node and Switch Definitions

These are the definitions and parameters used for deploying the demonstrated fabric:

Wiring

Hypervisor Node

Bare Metal Worker Node

Fabric Configuration

Updating Cumulus Linux

As a best practice, make sure to use the latest released Cumulus Linux NOS version.

For information on how to upgrade Cumulus Linux, refer to the Cumulus Linux User Guide.

Configuring the Cumulus Linux Switch

The SN3700 switch (hs-switch), is configured as follows:

            

            
nv set bridge domain br_hs untagged 1
nv set interface swp1-2 bridge domain br_hs
nv set interface swp1-2 link state up
nv set interface swp1-2 type swp
nv config apply -y
nv config save -y
        

The SN2201 switch (mgmt-switch) is configured as follows:

            

            
nv set interface swp1-2 link state up
nv set interface swp1-2 type swp
nv set interface swp1-2 bridge domain br_default
nv set bridge domain br_default untagged 1
nv config apply
nv config save -y
        

Host Configuration

No change from the Reference Deployment Guide (Baseline RDG) (Section "Deployment and Configuration", Subsection " Host Configuration ").

Hypervisor Installation and Configuration

No change from the Baseline RDG (Section "Deployment and Configuration", Subsection "Hypervisor Installation and Configuration").

Prepare Infrastructure Servers

No change from the Baseline RDG (Section "Deployment and Configuration", Subsection "Prepare Infrastructure Servers") regarding Firewall VM, Jump VM, MaaS VM.

Provision Master VMs Using MaaS

No change from the Baseline RDG (Section "Deployment and Configuration", Subsection "Provision Master VMs Using MaaS").

K8s Cluster Deployment and Configuration

The procedures for initial Kubernetes cluster deployment using Kubespray for the master nodes, and subsequent verification, remain unchanged from the Baseline RDG (Section "K8s Cluster Deployment and Configuration", Subsections: "Kubespray Deployment and Configuration", "Deploying Cluster Using Kubespray Ansible Playbook","K8s Deployment Verification".

DPF Installation

The DPF installation process (Operator, System components) largely follows the Baseline RDG.

Software Prerequisites and Required Variables

1. Start by installing the remaining software perquisites.

   Jump Node Console

   Collapse Source

   Copy

   Copied!

               
   
               
   ## Connect to master1 to copy helm client utility that was installed during kubespray deployment
   $ depuser@jump:~$ ssh master1
   depuser@master1:~$ cp /usr/local/bin/helm /tmp/
    
   ## In another tab 
   depuser@jump:~$ scp master1:/tmp/helm /tmp/
   depuser@jump:~$ sudo chown root:root /tmp/helm
   depuser@jump:~$ sudo mv /tmp/helm /usr/local/bin/
    
   ## Verify that envsubst utility is installed 
   depuser@jump:~$ which envsubst
   /usr/bin/envsubst
           

2. Proceed to clone the doca-platform Git repository:

   Jump Node Console

   Collapse Source

   Copy

   Copied!

               
   
               
   $ git clone https://github.com/NVIDIA/doca-platform.git
           

3. Change directory to doca-platform and checkout to tag v25.10.0:

   Jump Node Console

   Collapse Source

   Copy

   Copied!

               
   
               
   $ cd doca-platform/
   $ git checkout v25.10.0
           

4. Before deploying the objects under doca-platform/dpuservices/dts-blueman/directory, a few adjustments are required. Create a directory from where all the commands will be run:

   Jump Node Console

   Collapse Source

   Copy

   Copied!

               
   
               
   $ mkdir doca-platform/dpuservices/dts-blueman/
   $ cd doca-platform/dpuservices/dts-blueman/
           

5. Modify the variables in envvars.env to fit your environment, then source the file:

   envvars.env

   Collapse Source

   Copy

   Copied!

               
   
               
   ## IP Address for the Kubernetes API server of the target cluster on whih DPF is installed.
   ## This should never include a scheme or a port.
   ## e.g. 10.10.10.10
   export TARGETCLUSTER_API_SERVER_HOST=10.0.110.10
    
   ## Virtual IP used by the load balancer for the DPU Cluster. Must be a reserved IP from the management subnet and not
   ## allocated by DHCP.
   export DPUCLUSTER_VIP=10.0.110.200
    
   ## Interface on which the DPUCluster load balancer will listen. Should be the management interface of the control plane node.
   export DPUCLUSTER_INTERFACE=ens160
    
   ## IP address to the NFS server used as storage for the BFB.
   export NFS_SERVER_IP=10.0.110.253
    
   ## The repository URL for the NVIDIA Helm chart registry.
   ## Usually this is the NVIDIA Helm NGC registry. For development purposes, this can be set to a different repository.
   export HELM_REGISTRY_REPO_URL=https://helm.ngc.nvidia.com/nvidia/doca
    
   ## The DPF REGISTRY is the Helm repository URL where the DPF Operator Chart resides.
   ## Usually this is the NVIDIA Helm NGC registry. For development purposes, this can be set to a different repository.
   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.10.0
    
   ## URL to the BFB used in the `bfb.yaml` and linked by the DPUSet.
   export BFB_URL="http://nbu-nfs.mellanox.com/auto/sw_mc_soc_release/doca_dpu/doca_3.2.0/20251105/bfbs/pk/bf-bundle-3.2.0-107_25.10_ubuntu-24.04_prod.bfb"
    
   ## IP_RANGE_START and IP_RANGE_END
   ## These define the IP range for DPU discovery via Redfish/BMC interfaces
   ## Example: If your DPUs have BMC IPs in range 10.0.110.201-224
    
   ## Start of DPUDiscovery IpRange
   export IP_RANGE_START=10.0.110.205
    
   ## End of DPUDiscovery IpRange
   export IP_RANGE_END=10.0.110.205
    
   # The password used for DPU BMC root login, must be the same for all DPUs
   # For more information on how to set the BMC root password refer to BlueField DPU Administrator Quick Start Guide. 
   export BMC_ROOT_PASSWORD=<set your BMC_ROOT_PASSWORD>
           

6. Export environment variables for the installation:

   Jump Node Console

   Collapse Source

   Copy

   Copied!

               
   
               
   $ source envvars.env
           

DPF Operator Installation

No change from the Baseline RDG (Section "DPF Installation", Subsection "DPF Operator Installation").

DPF System Installation

No change from the Baseline RDG (Section "DPF Installation", Subsection "DPF System Installation").

DPU Service Installation

Change the DPUDeployment, DPUServiceConfiguration, DPUServiceTemplate yaml files.

Before deploying the objects under doca-platform/dpuservices/dts-blueman/directory, a few adjustments are required.

1. Create the following YAML to define a BFB resource that downloads the Bluefield Bitstream to a shared volume :

   bfb.yaml

   Collapse Source

   Copy

   Copied!

               
   
               
   ---
   apiVersion: provisioning.dpu.nvidia.com/v1alpha1
   kind: BFB
   metadata:
     name: bf-bundle
     namespace: dpf-operator-system
   spec:
     url: $BFB_URL
           

2. Create the DPUFlavor using the following YAML:

   DPUFlavor.yaml

   Collapse Source

   Copy

   Copied!

               
   
               
   ---
   apiVersion: provisioning.dpu.nvidia.com/v1alpha1
   kind: DPUFlavor
   metadata:
     name: dpf-provisioning-dts-blueman
     namespace: dpf-operator-system
   spec:
     bfcfgParameters:
       - UPDATE_ATF_UEFI=yes
       - UPDATE_DPU_OS=yes
       - WITH_NIC_FW_UPDATE=yes
     configFiles:
       - operation: override
         path: /etc/mellanox/mlnx-bf.conf
         permissions: "0644"
         raw: |
           ALLOW_SHARED_RQ="no"
           IPSEC_FULL_OFFLOAD="no"
           ENABLE_ESWITCH_MULTIPORT="yes"
       - operation: override
         path: /etc/mellanox/mlnx-ovs.conf
         permissions: "0644"
         raw: |
           CREATE_OVS_BRIDGES="no"
           OVS_DOCA="yes"
       - operation: override
         path: /etc/mellanox/mlnx-sf.conf
         permissions: "0644"
         raw: ""
     grub:
       kernelParameters:
         - console=hvc0
         - console=ttyAMA0
         - earlycon=pl011,0x13010000
         - fixrttc
         - net.ifnames=0
         - biosdevname=0
         - iommu.passthrough=1
         - cgroup_no_v1=net_prio,net_cls
         - hugepagesz=2048kB
         - hugepages=3072
     nvconfig:
       - device: '*'
         parameters:
           - PF_BAR2_ENABLE=0
           - PER_PF_NUM_SF=1
           - PF_TOTAL_SF=20
           - PF_SF_BAR_SIZE=10
           - NUM_PF_MSIX_VALID=0
           - PF_NUM_PF_MSIX_VALID=1
           - PF_NUM_PF_MSIX=228
           - INTERNAL_CPU_MODEL=1
           - INTERNAL_CPU_OFFLOAD_ENGINE=0
           - SRIOV_EN=1
           - NUM_OF_VFS=46
           - LAG_RESOURCE_ALLOCATION=1
           - LINK_TYPE_P1=ETH
           - LINK_TYPE_P2=ETH
     ovs:
       rawConfigScript: |
         _ovs-vsctl() {
           ovs-vsctl --no-wait --timeout 15 "$@"
         }
    
         _ovs-vsctl set Open_vSwitch . other_config:doca-init=true
         _ovs-vsctl set Open_vSwitch . other_config:dpdk-max-memzones=50000
         _ovs-vsctl set Open_vSwitch . other_config:hw-offload=true
         _ovs-vsctl set Open_vSwitch . other_config:pmd-quiet-idle=true
         _ovs-vsctl set Open_vSwitch . other_config:max-idle=20000
         _ovs-vsctl set Open_vSwitch . other_config:max-revalidator=5000
         _ovs-vsctl set Open_vSwitch . other_config:ctl-pipe-size=1024
         _ovs-vsctl --if-exists del-br ovsbr1
         _ovs-vsctl --if-exists del-br ovsbr2
         _ovs-vsctl --may-exist add-br br-sfc
         _ovs-vsctl set bridge br-sfc datapath_type=netdev
         _ovs-vsctl set bridge br-sfc fail_mode=secure
         _ovs-vsctl --may-exist add-port br-sfc p0
         _ovs-vsctl set Interface p0 type=dpdk
         _ovs-vsctl set Port p0 external_ids:dpf-type=physical
    
         _ovs-vsctl set Open_vSwitch . external-ids:ovn-bridge-datapath-type=netdev
         _ovs-vsctl --may-exist add-br br-ovn
         _ovs-vsctl set bridge br-ovn datapath_type=netdev
         _ovs-vsctl br-set-external-id br-ovn bridge-id br-ovn
         _ovs-vsctl br-set-external-id br-ovn bridge-uplink puplinkbrovntobrsfc
         _ovs-vsctl --may-exist add-port br-ovn pf0hpf
         _ovs-vsctl set Interface pf0hpf type=dpdk
           

3. Create the DPUDeployment.yaml file:

   DPUDeployment.yaml

   Collapse Source

   Copy

   Copied!

               
   
               
   ---
   apiVersion: svc.dpu.nvidia.com/v1alpha1
   kind: DPUDeployment
   metadata:
     name: dts-blueman
     namespace: dpf-operator-system
   spec:
     dpus:
       bfb: bf-bundle
       dpuSets:
       - nameSuffix: dpuset-dts-blueman
         nodeSelector:
           matchLabels:
             feature.node.kubernetes.io/dpu-enabled: "true"
         dpuSelector:
           provisioning.dpu.nvidia.com/dpudevice-service-name: dts-blueman
       flavor: dpf-provisioning-dts-blueman
       nodeEffect:
         noEffect: true
     services:
       dts:
         serviceTemplate: dts
         serviceConfiguration: dts
       blueman:
         serviceTemplate: blueman
         serviceConfiguration: blueman
           

4. Create the DPUServiceconfig_dts.yaml file:

   DPUServiceconfig_dts.yaml

   Collapse Source

   Copy

   Copied!

               
   
               
   ---
   apiVersion: svc.dpu.nvidia.com/v1alpha1
   kind: DPUServiceConfiguration
   metadata:
     name: dts
     namespace: dpf-operator-system
   spec:
     deploymentServiceName: "dts"
           

5. Create the DPUServicetemplate_dts.yaml file:

   DPUServicetemplate_dts.yaml

   Collapse Source

   Copy

   Copied!

               
   
               
   ---
   apiVersion: svc.dpu.nvidia.com/v1alpha1
   kind: DPUServiceTemplate
   metadata:
     name: dts
     namespace: dpf-operator-system
   spec:
     deploymentServiceName: "dts"
     helmChart:
       source:
         repoURL: $HELM_REGISTRY_REPO_URL
         version: 1.0.8
         chart: doca-telemetry
           

6. Create the DPUServiceconfig_blueman.yaml file:

   DPUServiceconfig_blueman.yaml

   Collapse Source

   Copy

   Copied!

               
   
               
   ---
   apiVersion: svc.dpu.nvidia.com/v1alpha1
   kind: DPUServiceConfiguration
   metadata:
     name: blueman
     namespace: dpf-operator-system
   spec:
     deploymentServiceName: "blueman"
           

7. Create the DPUServicetemplate_blueman.yaml file:

   DPUServiceTemplate.yaml

   Collapse Source

   Copy

   Copied!

               
   
               
   ---
   apiVersion: svc.dpu.nvidia.com/v1alpha1
   kind: DPUServiceTemplate
   metadata:
     name: blueman
     namespace: dpf-operator-system
   spec:
     deploymentServiceName: "blueman"
     helmChart:
       source:
         repoURL: $HELM_REGISTRY_REPO_URL
         version: 1.0.8
         chart: doca-blueman
           

8. Apply all of the YAML files mentioned above using the following command:

   Jump Node Console

   Collapse Source

   Copy

   Copied!

               
   
               
   $ cat *.yaml | envsubst | kubectl apply -f -
           

9. To follow the progress of DPU provisioning, run the following command to check its current phase:

   Jump Node Console

   Collapse Source

   Copy

   Copied!

               
   
               
   $ watch -n10 "kubectl describe dpu -n dpf-operator-system | grep 'Node Name\|Type\|Last\|Phase'"
   Every 10.0s: kubectl describe dpu -n dpf-operator-system | grep 'Node Name\|Type\|Last\|Phase'                                                                           
    
     Dpu Node Name:                                    dpu-node-mt24386019aq
       Last Transition Time:  2026-01-18T13:35:01Z
       Type:                  Initialized
       Last Transition Time:  2026-01-18T13:35:02Z
       Type:                  BFBReady
       Last Transition Time:  2026-01-18T13:35:02Z
       Type:                  NodeEffectReady
       Last Transition Time:  2026-01-18T13:35:03Z
       Type:                  InterfaceInitialized
       Last Transition Time:  2026-01-18T13:35:04Z
       Type:                  FWConfigured
       Last Transition Time:  2026-01-18T13:35:04Z
       Type:                  BFBPrepared
       Last Transition Time:  2026-01-18T13:44:56Z
       Type:                  OSInstalled
       Last Transition Time:  2026-01-18T13:47:59Z
       Type:                  Rebooted
     Phase:  Rebooting
           

10. Wait for the Rebooted stage and then Power Cycle the bare-metal host manual.

    After the DPU is up, run following command for each DPU worker:

    Jump Node Console

    Collapse Source

    Copy

    Copied!

                
    
                
    $ kubectl -n dpf-operator-system annotate dpunode mt24386019aq provisioning.dpu.nvidia.com/dpunode-external-reboot-required-
            

11. At this point, the DPU workers should be added to the cluster. As they being added to the cluster, the DPUs are provisioned.

    Jump Node Console

    Collapse Source

    Copy

    Copied!

                
    
                
    $ watch -n10 "kubectl describe dpu -n dpf-operator-system | grep 'Node Name\|Type\|Last\|Phase'"
    Every 10.0s: kubectl describe dpu -n dpf-operator-system | grep 'Node Name\|Type\|Last\|Phase'                                                                           
     
      Dpu Node Name:                                    dpu-node-mt24386019aq
        Type:       InternalIP
        Type:       Hostname
        Last Transition Time:  2026-01-18T13:35:01Z
        Type:                  Initialized
        Last Transition Time:  2026-01-18T13:35:02Z
        Type:                  BFBReady
        Last Transition Time:  2026-01-18T13:35:02Z
        Type:                  NodeEffectReady
        Last Transition Time:  2026-01-18T13:35:03Z
        Type:                  InterfaceInitialized
        Last Transition Time:  2026-01-18T13:35:04Z
        Type:                  FWConfigured
        Last Transition Time:  2026-01-18T13:35:04Z
        Type:                  BFBPrepared
        Last Transition Time:  2026-01-18T13:44:56Z
        Type:                  OSInstalled
        Last Transition Time:  2026-01-18T13:55:40Z
        Type:                  Rebooted
        Last Transition Time:  2026-01-18T13:55:40Z
        Type:                  DPUClusterReady
        Last Transition Time:  2026-01-18T13:55:41Z
        Type:                  Ready
      Phase:  Ready
            

12. Finally, validate that all the different DPU-related objects are now in the Ready state:

    Jump Node Console

    Collapse Source

    Copy

    Copied!

                
    
                
    $ echo 'alias dpfctl="kubectl -n dpf-operator-system exec deploy/dpf-operator-controller-manager -- /dpfctl "' >> ~/.bashrc
     
    $ dpfctl describe dpudeployments
    NAME                                           NAMESPACE            STATUS       REASON    SINCE  MESSAGE
    DPFOperatorConfig/dpfoperatorconfig            dpf-operator-system  Ready: True  Success   19m
    └─DPUDeployments
      └─DPUDeployment/dts-blueman                  dpf-operator-system  Ready: True  Success   19m
        ├─DPUSets
        │ └─DPUSet/dts-blueman-dpuset-dts-blueman  dpf-operator-system  Ready: True  Success   19m
        │   ├─BFB/bf-bundle                        dpf-operator-system  Ready: True  Ready     20m    File: bf-bundle-3.2.1-34_25.11_ubuntu-24.04_64k_prod.bfb, DOCA: 3.2.1
        │   ├─DPUNodes
        │   │ └─1 DPUNodes...                      dpf-operator-system  Ready: True  Ready     19m    See dpu-node-mt24386019aq
        │   └─DPUs
        │     └─1 DPUs...                          dpf-operator-system  Ready: True  DPUReady  19m    See dpu-node-mt24386019aq-mt24386019aq                                                                                          
        └─Services
          ├─DPUServiceTemplates
          │ ├─DPUServiceTemplate/blueman           dpf-operator-system  Ready: True  Success   20m
          │ └─DPUServiceTemplate/dts               dpf-operator-system  Ready: True  Success   20m
          └─DPUServices
            └─2 DPUServices...                     dpf-operator-system  Ready: True  Success   19m    See blueman-7dphr, dts-m5m8f
     
     
     
    $ echo "alias ki='KUBECONFIG=/home/depuser/dpu-cluster.config kubectl'" >> ~/.bashrc
    $ kubectl get secrets -n dpu-cplane-tenant1 dpu-cplane-tenant1-admin-kubeconfig -o json | jq -r '.data["admin.conf"]' | base64 --decode > /home/depuser/dpu-cluster.config 
    $ ki get node -A
    NAME                                 STATUS   ROLES    AGE     VERSION
    dpu-node-mt24386019aq-mt24386019aq   Ready    <none>   21m   v1.34.3
     
    $ kubectl get dpu -A
    NAMESPACE             NAME                                 READY   PHASE   AGE
    dpf-operator-system   dpu-node-mt24386019aq-mt24386019aq   True    Ready   22m
     
    $ kubectl wait --for=condition=ready --namespace dpf-operator-system dpu --all
    dpu.provisioning.dpu.nvidia.com/dpu-node-mt24386019aq-mt24386019aq condition met
            

Verification

Here's a step-by-step procedure to check the DTS and Blueman DPUServices were deployed on your NVIDIA BlueField DPU.

To be able to log into BlueMan and view the local DTS instance data in a convenient way, the management IP address of the DPU should be entered to a web browser located in the same network as the DPU. In this RDG, it will be demonstrated by using RDP to connect to the Jump node and opening a web browser in it (same as with MaaS, Firewall).

1. To find out the DPU management IP address in the 10.0.110.0/24 subnet, obtain the DPU names .

   Jump Node Console

   Collapse Source

   Copy

   Copied!

               
   
               
   $ kubectl get dpus -n dpf-operator-system
   NAME                                 READY   PHASE   AGE
   dpu-node-mt24386019aq-mt24386019aq   True    Ready   24m
           

2. Obtain the DPU management IP :

   Jump Node Console

   Collapse Source

   Copy

   Copied!

               
   
               
   $ kubectl get dpus -n dpf-operator-system -o json | jq '.items[].status.addresses[0].address' | cut -d '"' -f210.0.110.215
           

3. In the RDP session, open a web browser and enter https://<DPU_INTERNAL_IP>. A warning of self-signed certificate should appear; click accept the risk and proceed.

   Afterwards it will open the login page:

   

   The login credentials to use are the same pair used for the SSH connection to the DPU ( ubuntu/ubuntu ). However, login straight away won't work and an additional certificate exception in the browser has to be made.

4. Open another tab in the browser and enter https://<DPU_INTERNAL_IP>:10000. It will again prompt a warning of self-signed certificate; click accept the risk to add it to your browser exception list. An error message similar to the following will be displayed, but it doesn't matter since it's an internal address to fetch resources from–in other words, the error message can be ignored.

   

5. Return to the BlueMan login page, enter the credentials, and you should be able to login.

   

Done.

Authors

Boris Kovalev Boris Kovalev has worked for the past several years as a Solutions Architect, focusing on NVIDIA Networking/Mellanox technology, and is responsible for complex machine learning, Big Data and advanced VMware-based cloud research and design. Boris previously spent more than 20 years as a senior consultant and solutions architect at multiple companies, most recently at VMware. He has written multiple reference designs covering VMware, machine learning, Kubernetes, and container solutions which are available at the NVIDIA Documents website.

NVIDIA, the NVIDIA logo, and BlueField are trademarks and/or registered trademarks of NVIDIA Corporation in the U.S. and other countries. Other company and product names may be trademarks of the respective companies with which they are associated. ^TM

© 2025 NVIDIA Corporation. All rights reserved.

This document is provided for information purposes only and shall not be regarded as a warranty of a certain functionality, condition, or quality of a product. NVIDIA Corporation (“NVIDIA”) makes no representations or warranties, expressed or implied, as to the accuracy or completeness of the information contained in this document and assumes no responsibility for any errors contained herein. NVIDIA shall have no liability for the consequences or use of such information or for any infringement of patents or other rights of third parties that may result from its use. This document is not a commitment to develop, release, or deliver any Material (defined below), code, or functionality. NVIDIA reserves the right to make corrections, modifications, enhancements, improvements, and any other changes to this document, at any time without notice. Customer should obtain the latest relevant information before placing orders and should verify that such information is current and complete. NVIDIA products are sold subject to the NVIDIA standard terms and conditions of sale supplied at the time of order acknowledgement, unless otherwise agreed in an individual sales agreement signed by authorized representatives of NVIDIA and customer (“Terms of Sale”). NVIDIA hereby expressly objects to applying any customer general terms and conditions with regards to the purchase of the NVIDIA product referenced in this document. No contractual obligations are formed either directly or indirectly by this document.