Logo

Contents:

  • Destination Earth Data Lake Introduction
  • Discovery and Data Access
  • Edge Services - Big Data Processing Services
  • Interfaces (Endpoints)
  • DestinE Platform for DEDL users
  • My DataLake Services
  • Working with AI in the Data Lake
    • MLOps Studio
      • Access the MLOps Studio workspace
      • Create and manage a MLOps Studio namespace
      • Download and use kubeconfig for a MLOps Studio namespace
      • Use the MLOps Studio dashboard
      • Notebook Servers
      • Access a MLOps Studio notebook environment with Visual Studio Code Remote Tunnels
      • Access a MLOps Studio notebook environment with kubectl port-forward
      • Choose how to run Python workloads in MLOps Studio
      • Run Python code in a MLOps Studio notebook environment
      • Run Python code as a MLOps Studio PyTorchJob
      • Access MLOps Studio Pipelines API from outside the cluster
      • MLOps Studio Pipelines: Accessing Model Registry via Istio
      • Use DEDL standalone S3 object storage with KServe
      • Choosing Gloo or NCCL for Distributed PyTorch Training in PyTorchJob
      • Known limitations in MLOps Studio
      • MLOps Studio Scenarios
        • General MLOps Studio acceptance test scenarios
        • Katib scenarios
        • KServe
        • MLOps Studio Trainer
        • Model Registry
        • Notebooks
        • Pipelines
        • Security - preventing container escape on a shared Kubernetes / Kubeflow cluster
        • Spark
        • MLOps Studio TensorBoard PVC Smoke Test
  • FAQs
  • Privacy Notice
  • Terms and Conditions
Destination Earth Data Lake
  • »
  • Working with AI in the Data Lake »
  • MLOps Studio »
  • MLOps Studio Scenarios »
  • Model Registry
  • DestinE Data Lake portal

Model Registry

  • Model Registry
    • Prerequisites
    • Overview
    • Testing from the web interface
    • Testing from notebooks
    • Testing from pipelines
    • Troubleshooting
    • Quick reference
    • Appendix: useful commands
    • What to do next
  • Model Registry scenarios
    • Overview
    • Prerequisites
    • Scenario 1. Add a model to Model Registry from a notebook
    • Scenario 2. Error on model name duplication
    • Scenario 3. Input data validation during model registration
    • Scenario 4. Model versioning from a notebook using the SDK in a virtual environment
    • Scenario 5. Happy path: register a model and version from MLOps Studio Pipelines
    • Scenario 6. Rerun by cloning the same pipeline run
    • Scenario 7. Incorrect Model Registry endpoint in a pipeline
    • Scenario 8. Register multiple model versions in the Model Registry from a pipeline
    • Scenario 9. Happy path: register a model and version directly in the Model Registry UI, then add a new version
    • Scenario 10. Error when attempting to add a model that already exists
    • What to do next
  • Serve a model from Model Registry with KServe
    • Overview
    • Prerequisites
    • Namespace variable
    • What this test verifies
    • Step 0. Optional cleanup of stale pods
    • Step 1. Create the inference payload
    • Step 2. Deploy the InferenceService
    • Step 3. Wait for readiness and collect diagnostics
    • Step 4. Public test and SSO versus DNS detection
    • Step 5. DNS workaround with –resolve
    • Step 6. Direct-to-pod test to bypass ingress and authentication
    • Cleanup
    • What to do next
Previous Next

© Copyright 2026, CloudFerro.