replicatedhq / replicatedhq/platform-examples

feat(mlflow): add license field wiring pattern (KOTS Config to app ConfigMap)

Open
#168 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

Wire KOTS license entitlements through Config → HelmChart CR values → application ConfigMap so the app can consume license fields like tier and max_users.

Scope

  • Add Config items to release/kots-config.yaml using {{repl LicenseFieldValue "tier"}} and {{repl LicenseFieldValue "max_users"}}
  • Map Config items into HelmChart CR values in release/mlflow-chart.yaml as values.license.*
  • Create charts/mlflow/templates/license-configmap.yaml that reads .Values.license.* and creates a ConfigMap for app consumption
  • Add license section to charts/mlflow/values.yaml with defaults

Files touched

  • applications/mlflow/release/kots-config.yaml (add license Config items)
  • applications/mlflow/release/mlflow-chart.yaml (add license values mapping)
  • applications/mlflow/charts/mlflow/templates/license-configmap.yaml (new file)
  • applications/mlflow/charts/mlflow/values.yaml (add license section)

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 the existing patterns in applications/mlflow/release/kots-config.yaml and applications/mlflow/release/mlflow-chart.yaml, then inspect charts/mlflow/values.yaml and its templates. Add the tier and max_users flow across the four named files, and verify that the resulting application ConfigMap exposes those license fields when deployed through the integration branch.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
devops, infrastructure
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.