Chapter 5. Deploy an AutoML model for inference


After you register a model from the AutoML leaderboard, you can deploy it for inference with the AutoGluon serving runtime. Deploying the model creates a REST API endpoint that you can use to send prediction requests.

Prerequisites

  • You have registered a model from the AutoML leaderboard to a model registry. For more information, see Evaluate AutoML results.
  • An administrator has added the AutoGluon serving runtime to your cluster by following the steps in Adding a custom model-serving runtime with the following ServingRuntime definition:

    Example ServingRuntime with AutoGluon

    apiVersion: serving.kserve.io/v1alpha1
    kind: ServingRuntime
    metadata:
      name: kserve-autogluonserver
      annotations:
        openshift.io/display-name: "AutoGluon ServingRuntime for KServe"
    spec:
      annotations:
        prometheus.kserve.io/port: "8080"
        prometheus.kserve.io/path: "/metrics"
      supportedModelFormats:
        - name: autogluon
          version: "1"
      protocolVersions:
        - v1
        - v2
      containers:
        - name: kserve-container
          image: registry.redhat.io/rhoai/odh-kserve-autogluon-server-rhel9@sha256:6d55374ef2e2ac09d772701a72d2ea370c57c34eb89c7b7a71ee204559c699a3
          args:
            - --model_name={{.Name}}
            - --model_dir=/mnt/models
            - --http_port=8080
          securityContext:
            allowPrivilegeEscalation: false
            privileged: false
            runAsNonRoot: true
            capabilities:
              drop:
                - ALL
          resources:
            requests:
              cpu: "1"
              memory: 2Gi
            limits:
              cpu: "1"
              memory: 2Gi

Procedure

  1. Deploy the registered model version from the model registry by following the steps in Deploying a model version from a model registry.

    Configure the deployment with the following values:

    • For Model framework, select autogluon - 1.
    • For Serving runtime, select AutoGluon ServingRuntime for KServe.

      Important

      If you are deploying a time series forecasting model and your training data used column names other than item_id and timestamp, you must add custom runtime environment variables before deploying. See the following table.

      Expand
      Table 5.1. Custom runtime environment variables for time series models with non-default column names
      Environment variableDescription

      AUTOGLUON_TS_ID_COLUMN

      The name of the column that identifies each time series. Set this variable if the column is not named item_id.

      AUTOGLUON_TS_TIMESTAMP_COLUMN

      The name of the column that has the date or time values. Set this variable if the column is not named timestamp.

      Add these variables under Advanced settings with the same column names that you specified when you created the optimization run.

Verification

  • On the Deployments page, verify that the model deployment shows a status of Ready.
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat Documentation

Legal Notice

Theme

© 2026 Red Hat
Back to top