live wire
▸AI · Red Hat documents usage-based admission fair sharing for Kueue 1.4 on OpenShiftRed Hat Developer▸AI: Red Hat maps governed firewall changes from ServiceNow through Ansible and two human approval gatesRed Hat Developer▸CLUSTER MGMT · ACM 2.17 makes Submariner 0.24 GA with Important-rated fixesRed Hat Errata▸PLATFORM · Red Hat makes on-premises Lightspeed recommendations GA for Satellite 6.18Red Hat Errata▸SECURITY · Red Hat Hardened Images updates Tomcat 10 for nine authentication, access-control and DoS flawsRed Hat Errata▸AI · Open Data Hub 3.6.0 EA1 bundles Trainer, MLflow and llm-d componentsOpen Data Hub▸AI · Speculators 0.6.0 adds P-EAGLE parallel drafting for vLLM speculative decodingRed Hat Developer▸SECURITY · OpenShift 4.17.57 fixes seven Go and TLS CVEs in an Important-rated updateRed Hat Errata▸AI · Red Hat benchmarks local LLM guardrails with EvalHub, exposing regex accuracy and latency trade-offsRed Hat Developer▸AI · Red Hat maps silent tool-call failures across agentic pipelinesRed Hat▸API · Kuadrant 1.5.3 adds GRPCRoute policies and developer-portal API-key workflowsKuadrant▸AI · (Aug 25) IBM releases Apache-2.0 Granite 4.2 reasoning models in 3B, 8B and 30B sizesIBM Research▸JAVA · Red Hat build of Quarkus 3.33.3.SP1 fixes 13 CVEs in an Important-rated updateRed Hat errata▸AI · vLLM moves Kimi K2 RL weight sync across 384 H100s in 7.53 seconds (Aug 22)vLLM▸AI · Red Hat documents usage-based admission fair sharing for Kueue 1.4 on OpenShiftRed Hat Developer▸AI: Red Hat maps governed firewall changes from ServiceNow through Ansible and two human approval gatesRed Hat Developer▸CLUSTER MGMT · ACM 2.17 makes Submariner 0.24 GA with Important-rated fixesRed Hat Errata▸PLATFORM · Red Hat makes on-premises Lightspeed recommendations GA for Satellite 6.18Red Hat Errata▸SECURITY · Red Hat Hardened Images updates Tomcat 10 for nine authentication, access-control and DoS flawsRed Hat Errata▸AI · Open Data Hub 3.6.0 EA1 bundles Trainer, MLflow and llm-d componentsOpen Data Hub▸AI · Speculators 0.6.0 adds P-EAGLE parallel drafting for vLLM speculative decodingRed Hat Developer▸SECURITY · OpenShift 4.17.57 fixes seven Go and TLS CVEs in an Important-rated updateRed Hat Errata▸AI · Red Hat benchmarks local LLM guardrails with EvalHub, exposing regex accuracy and latency trade-offsRed Hat Developer▸AI · Red Hat maps silent tool-call failures across agentic pipelinesRed Hat▸API · Kuadrant 1.5.3 adds GRPCRoute policies and developer-portal API-key workflowsKuadrant▸AI · (Aug 25) IBM releases Apache-2.0 Granite 4.2 reasoning models in 3B, 8B and 30B sizesIBM Research▸JAVA · Red Hat build of Quarkus 3.33.3.SP1 fixes 13 CVEs in an Important-rated updateRed Hat errata▸AI · vLLM moves Kimi K2 RL weight sync across 384 H100s in 7.53 seconds (Aug 22)vLLM
upstreambeat.ai
guideAI

Red Hat and DagsHub connect private MLOps workflows on OpenShift AI

A new quickstart joins dataset versioning, experiment tracking and model management, but teams need DagsHub licensing and an MLflow proxy boundary.

By The News Desk· Aug 21, 2026

Red Hat and DagsHub have published an OpenShift AI quickstart that puts dataset versioning, annotation, experiment tracking and model management into one cluster-based workflow. The useful part is not the promise of a “unified” platform; it is the concrete integration work required to make DagsHub and OpenShift AI’s shared MLflow service agree on identity and workspace boundaries.

What the quickstart deploys

The reference workflow installs DagsHub in an OpenShift namespace, exposes it through an OpenShift route and adds a Jupyter workbench with an end-to-end retrieval-augmented generation tutorial. The example builds an IT support chatbot, compares prompt and model combinations, and records evaluation results with MLflow.

DagsHub supplies Git-backed code and data workflows alongside DVC, MLflow and Label Studio integrations. OpenShift AI remains the execution environment for workbenches, training and inference. In the quickstart, that separation gives teams a single place to track data, code, experiments and models without moving the whole workflow to a hosted MLOps service.

The integration boundary matters

OpenShift AI 3.4 and later uses an X-MLFLOW-WORKSPACE request header to scope calls to its cluster-wide MLflow instance. DagsHub’s client does not add that header itself, so the quickstart deploys an OpenResty proxy between DagsHub and MLflow.

The proxy injects the namespace as the workspace, authenticates with a dedicated service account carrying MLflow RBAC roles, and removes an unsupported artifact_location field from experiment-creation requests. That is the most transferable engineering detail in the design: the MLOps tools are connected through a narrow translation and authorization layer rather than by weakening the platform’s tenancy controls.

What teams need before trying it

This is not a zero-dependency community install. Red Hat’s instructions require OpenShift 4.20 or later, OpenShift AI 3.4 or later, cluster-admin access, persistent storage and DagsHub enterprise credentials. The documented small-team sizing starts at 4 vCPUs and 8 GB of memory, with 8 vCPUs and 16 GB recommended, plus 100 GB of persistent storage. The cluster also needs outbound access to DagsHub’s Google-hosted container registries.

Teams evaluating the pattern should first decide whether the licensing, registry access and cluster-admin installation fit their operating model. If they do, the quickstart is a practical starting point for testing reproducibility and private data control. If they do not, the MLflow proxy design is still worth studying as an example of adapting a third-party client to OpenShift AI’s workspace isolation without bypassing it.

sources

Filed by The News Desk. Corrections: desk@upstreambeat.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.

    more from the desk