[FR] Image generation endpoint type for MLflow Deployments Server providers

Willingness to contribute

Yes. I can contribute this feature independently.

Proposal Summary

Include image generation endpoint type (image/v1/generation) for MLflow Deployments Server providers.

Motivation

What is the use case for this feature?

The feature aims to extend MLflow Deployments Server’s interface to include image generation alongside existing endpoints for completion, chat, and embedding models.

Why is this use case valuable to support for MLflow users in general?

Including image generation completes the suite of MLflow’s endpoint types, enhancing its utility and versatility for users.

Why is this use case valuable to support for your project(s) or organization?

Supporting this use case helps streamline and unify tools within the AI gateway use case.

Why is it currently difficult to achieve this use case?

NA.

Details

No response

What component(s) does this bug affect?

[ ] area/artifacts: Artifact stores and artifact logging
[ ] area/build: Build and test infrastructure for MLflow
[X] area/deployments: MLflow Deployments client APIs, server, and third-party Deployments integrations
[ ] area/docs: MLflow documentation pages
[ ] area/examples: Example code
[ ] area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
[ ] area/models: MLmodel format, model serialization/deserialization, flavors
[ ] area/recipes: Recipes, Recipe APIs, Recipe configs, Recipe Templates
[ ] area/projects: MLproject format, project running backends
[ ] area/scoring: MLflow Model server, model deployment tools, Spark UDFs
[X] area/server-infra: MLflow Tracking server backend
[ ] area/tracking: Tracking Service, tracking client APIs, autologging

What interface(s) does this bug affect?

[ ] area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
[ ] area/docker: Docker use across MLflow's components, such as MLflow Projects and MLflow Models
[ ] area/sqlalchemy: Use of SQLAlchemy in the Tracking Service or Model Registry
[ ] area/windows: Windows support

What language(s) does this bug affect?

[ ] language/r: R APIs and clients
[ ] language/java: Java APIs and clients
[ ] language/new: Proposals for new client languages

What integration(s) does this bug affect?

[ ] integrations/azure: Azure and Azure ML integrations
[ ] integrations/sagemaker: SageMaker integrations
[ ] integrations/databricks: Databricks integrations

mlflow / mlflow