Skip to content

Guidance needed for validating SR-IOV Operator on single-node Kubernetes cluster (Mellanox ConnectX-6 Lx) #968

@ashokpariya0

Description

@ashokpariya0

I am setting up and validating the SR-IOV Network Operator on a single-node Kubernetes cluster on s390x architecture
with Mellanox Technologies MT2894 Family [ConnectX-6 Lx] card
and would like guidance on what tests are recommended, or how validation should be performed in this type of setup.

# lspci
00f9:00:00.0 Ethernet controller: Mellanox Technologies ConnectX Family mlx5Gen Virtual Function
00fa:00:00.0 Ethernet controller: Mellanox Technologies ConnectX Family mlx5Gen Virtual Function
0108:00:00.0 Ethernet controller: Mellanox Technologies MT2894 Family [ConnectX-6 Lx]
0109:00:00.1 Ethernet controller: Mellanox Technologies MT2894 Family [ConnectX-6 Lx]
# oc get all -n sriov-network-operator
NAME                                          READY   STATUS    RESTARTS   AGE
pod/sriov-network-config-daemon-62tkl         1/1     Running   0          3h
pod/sriov-network-operator-5d7649b8b5-vpv6x   1/1     Running   0          3h

NAME                                         DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR                                                            AGE
daemonset.apps/sriov-device-plugin           0         0         0       0            0           kubernetes.io/os=linux,sriovnetwork.openshift.io/device-plugin=Enabled   3d17h
daemonset.apps/sriov-network-config-daemon   1         1         1       1            1           kubernetes.io/os=linux,node-role.kubernetes.io/worker=                   3d17h

NAME                                     READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/sriov-network-operator   1/1     1            1           3d17h

NAME                                                DESIRED   CURRENT   READY   AGE
replicaset.apps/sriov-network-operator-5d7649b8b5   1         1         1       3d17h

# kubectl get sriovnetworknodestates.sriovnetwork.openshift.io -n sriov-network-operator b314lp37.lnxne.boe -o yaml
apiVersion: sriovnetwork.openshift.io/v1
kind: SriovNetworkNodeState
metadata:
  annotations:
    sriovnetwork.openshift.io/current-state: Idle
    sriovnetwork.openshift.io/desired-state: Idle
  creationTimestamp: "2025-11-20T16:19:02Z"
  generation: 17
  name: b314lp37.lnxne.boe
  namespace: sriov-network-operator
  ownerReferences:
  - apiVersion: sriovnetwork.openshift.io/v1
    blockOwnerDeletion: true
    controller: true
    kind: SriovOperatorConfig
    name: default
    uid: eded8bfe-2514-45a0-b2df-7dff46a49094
  resourceVersion: "602583"
  uid: 9eb94f0e-19c5-4678-8704-ab861294c502
spec:
  bridges: {}
  system: {}
status:
  interfaces:
  - deviceID: 101f
    driver: mlx5_core
    eSwitchMode: legacy
    linkAdminState: up
    linkSpeed: 10000 Mb/s
    linkType: ETH
    mac: 9c:63:c0:53:06:82
    mtu: 1500
    name: ens2048f0np0
    pciAddress: "0108:00:00.0"
    totalvfs: 127
    vendor: 15b3
  - deviceID: 101f
    driver: mlx5_core
    eSwitchMode: legacy
    linkAdminState: up
    linkSpeed: 10000 Mb/s
    linkType: ETH
    mac: 9c:63:c0:53:06:83
    mtu: 1500
    name: ens2176f1np1
    pciAddress: "0109:00:00.1"
    totalvfs: 127
    vendor: 15b3
  syncStatus: Succeeded
  system:
    rdmaMode: shared

Environment
k8s (single-node, s390x)
Mellanox ConnectX-6 Lx (device ID 101f)
eSwitchMode: legacy
Firmware locked to 127 VFs
SR-IOV operator version: latest master

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions