Skip to main content
Version: Current

MLflow models registry integration

Enterprise

Description

Nussknacker ML Runtime can serve models registered in MLflow models registry. Once the MLflow integration is configured, Nussknacker will generate an ML Enricher component, which can be used in the scenario to infer ML models.

This document explains how to configure native MLflow integration.

Integration parameters

The configuration differs slightly depending on whether this is a self hosted MLflow installation or Databricks hosted.

Self-hosted MLflow secured with OAuth2

Use this configuration when connecting Nussknacker Cloud to a self-hosted MLflow Tracking Server protected by an OAuth2-compliant identity provider (e.g., Keycloak, Auth0, Okta, Azure AD, etc.) using the Client Credentials (M2M) OAuth2 flow.

  • Server URL:
    The base URL of your self-hosted MLflow Tracking Server.
    Example: https://mlflow.my-company.com

  • Token URL:
    The OAuth2 token endpoint provided by your identity provider, used to obtain access tokens for API calls.
    Example (Keycloak): https://auth.my-company.com/realms/<realm>/protocol/openid-connect/token

  • Client ID:
    The OAuth2 client ID registered in your identity provider.
    This identifies the Nussknacker client requesting access.

  • Client Secret:
    The secret associated with the registered client.

  • Scope (optional):
    The scope(s) required to access the MLflow server APIs.
    This is provider-specific and may be required depending on identity provider settings.__ Example: mlflow.read, api, or openid

Databricks-managed MLflow

Use this configuration when integrating with MLflow hosted on Databricks.

  • Server URL:
    Databricks instance URL.
    Example: https://dbc-a1b2345c-d6e7.cloud.databricks.com

  • Token URL:
    The Databricks OAuth2 token endpoint, formed by appending /oidc/v1/token to the Server URL (Databricks workspace URL).
    Example: https://dbc-a1b2345c-d6e7.cloud.databricks.com/oidc/v1/token

  • Client ID:
    The Service Principal client ID.

  • Client Secret:
    The Service Principal secret.

  • Scope:
    Must be set to: all-apis.__