Skip to content
 
 

Repository files navigation

MLflow Deployment

MLflow instance deployed on OpenShift via ArgoCD, with Kubernetes-native RBAC for per-experiment access control.

Instance

Resource URL
Web UI https://mlflow.apps.int.spoke.prod.us-west-2.aws.paas.redhat.com/
ArgoCD app mlflow in ambient-code--argocd
Namespace ambient-code--mlflow

Architecture

  • MLflow — OpenDataHub MLflow image with kubernetes-auth plugin
  • PostgreSQL — metadata store (experiments, runs, traces, metrics)
  • S3 — artifact store (s3://ambient-code-mlflow-artifacts/mlflow)
  • OAuth Proxy — browser authentication via OpenShift OAuth, forwards Bearer tokens to MLflow
  • kubernetes-auth — per-resource RBAC via Kubernetes SubjectAccessReview

Repository structure

kustomization.yaml          # Root kustomization (ArgoCD source)
rbac.yaml                   # Shared roles, CI SA, admin bindings
experiments/                # Per-experiment RBAC (self-contained kustomization)
  _template.yaml            # Onboarding template
  kustomization.yaml        # Add new experiment files here
  rfe-assessor.yaml         # Example: rfe-assessor experiment
bootstrap/                  # One-time cluster-admin resources
  it-grant.yaml             # RBAC escalation grant + auth-delegator
  mlflow-s3-iam-policy.json # IAM policy for the mlflow-s3 user (artifact store)
Containerfile               # Patched MLflow image build
patches/                    # Python patches applied by Containerfile

Documentation

  • docs/architecture.md — authorization flow, RBAC model, pod namespace fallback
  • docs/onboarding.md — granting a new agent access (experiment + scoped RBAC)
  • docs/usage.md — configuring a client to push traces (GitLab CI, agent-eval-harness, generic MLflow client)
  • docs/storage.md — artifact store (S3): proxied uploads, IAM policy, verification

About

MLflow deployment manifests for OpenShift (postgres, oauth-proxy, route)

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages