These guides cover deploying, configuring, and integrating Michelangelo in a Kubernetes environment. They target platform engineers and infrastructure operators who are responsible for running Michelangelo in production and for connecting it to the broader ML infrastructure their teams already use — experiment tracking, model registries, compute clusters, schedulers, and serving frameworks.
Getting Started
For a fresh deployment, follow this recommended reading order:
- Platform Setup — configure each component (API server, controller manager, worker, UI/Envoy) via ConfigMaps and Kustomize overlays
- Register a Compute Cluster — connect an existing Kubernetes cluster so Michelangelo can dispatch Ray and Spark jobs to it
- Cluster Setup for Serving — enable model inference on a local or remote cluster
- Authentication — connect an identity provider and configure RBAC before opening to users
Setup & Configuration
| Guide | Description |
|---|
| Helm Chart | Install the Michelangelo control plane with Helm — chart layout, values reference, and migration phases |
| Platform Setup | ConfigMaps and key fields for API server, controller manager, worker, and UI/Envoy |
| Network & Ingress | Envoy proxy, Ingress setup, TLS with cert-manager, and multi-cluster connectivity |
| Authentication | OIDC identity provider setup, RBAC, session configuration, multi-tenant isolation |
| Register a Compute Cluster | Connect an existing Kubernetes cluster to the Michelangelo control plane |
| Guide | Description |
|---|
| Model Registry | Operate Michelangelo's built-in model registry, configure storage and RBAC, and integrate with serving and CI/CD |
| Ingester Controller | Deploy, configure, and operate the ingester that syncs CRDs into MySQL |
Jobs & Compute
Model Serving
Third-Party Integrations
Michelangelo is designed to run alongside existing ML infrastructure. The guides below cover making external tools reachable from Michelangelo workloads.
Operations
Architecture & Reference