replicatedhq / replicatedhq/platform-examples

feat(mlflow): add GPU node scheduling pattern

Open
#170 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go Template
Stars
9
Forks
6
PR merge metrics
No merged PRs in 30d

Description

Parent epic: #166
Integration branch: feat/mlflow-enterprise-patterns

Add GPU scheduling support for ML/AI workloads with node selectors, tolerations, and nvidia.com/gpu resource limits.

Scope

  • Add gpu section to charts/mlflow/values.yaml: enabled: false, nodeSelector, tolerations, resources.limits["nvidia.com/gpu"]
  • Update charts/mlflow/templates/deployment.yaml to conditionally inject:
    • nodeSelector from .Values.gpu.nodeSelector when gpu.enabled
    • tolerations from .Values.gpu.tolerations when gpu.enabled
    • resources.limits including nvidia.com/gpu when gpu.enabled
  • Add comments explaining the pattern for vendors adapting it to AMD ROCm or other GPU providers

Files touched

  • applications/mlflow/charts/mlflow/values.yaml (add gpu section)
  • applications/mlflow/charts/mlflow/templates/deployment.yaml (conditional GPU blocks)

PR target

Branch PRs to feat/mlflow-enterprise-patterns (not main).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading applications/mlflow/charts/mlflow/values.yaml and applications/mlflow/charts/mlflow/templates/deployment.yaml on the feat/mlflow-enterprise-patterns branch. Add the disabled-by-default GPU settings, conditionally render node selectors, tolerations, and nvidia.com/gpu limits, and include vendor adaptation comments; done means the chart supports the requested GPU pattern without changing default behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
devops, machine-learning
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.