domains / families / devops / doca-flow-grpc-server

doca-flow-grpc-server

separate

Remote control of DOCA Flow over gRPC with the shipped `doca_flow_grpc` server: program Flow pipes and entries from Python, Go, Rust or Java, or from another host, instead of linking `libdoca_flow.so`. PLAINTEXT-ONLY: the server uses `grpc::InsecureServerCredentials()` with NO TLS / mTLS / token-auth knob; transport security must come from external infrastructure (e.g. an mTLS proxy / sidecar) on a trusted segment. Trigger even without "gRPC": "program Flow rules from Python on another host", "remotely configure pipes on the BlueField", "client times out connecting to the Flow server", "where is the .proto for Flow", "UNAUTHENTICATED / FAILED_PRECONDITION on a Flow RPC". Covers bringing up, configuring, hardening and debugging the server. Route elsewhere for the underlying doca-flow C API, generic gRPC tooling (protoc, language bindings), or DOCA install / BFB bring-up.

When to use

• program Flow pipes and entries from Python, Go, Rust or Java
• remotely configure pipes on the BlueField
• bring up, configure, harden and debug the server
• locate the .proto for Flow
• diagnose UNAUTHENTICATED or FAILED_PRECONDITION on a Flow RPC
• decide when to use gRPC vs direct libdoca_flow.so link

When not to use

• underlying doca-flow C API
• generic gRPC tooling (protoc, language bindings)
• DOCA install / BFB bring-up

Skill page

Source