replicatedhq / replicatedhq/platform-examples
feat(mlflow): add support bundle wrapper chart for PostgreSQL operator
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
Create a wrapper chart for CloudnativePG that includes support bundle specs, following the patterns/support-bundles pattern.
Scope
- Create
applications/mlflow/charts/postgres-support/Chart.yaml(wrapper chart, no application code) - Create
applications/mlflow/charts/postgres-support/templates/_supportbundle.tplwith:- CloudnativePG operator pod logs collector
- PostgreSQL cluster status collector
- PVC status collector
- Analyzer for common PostgreSQL failure modes
- Create
applications/mlflow/charts/postgres-support/templates/secret-supportbundle.yaml(support bundle spec as Secret) - Add the wrapper chart as a dependency in
applications/mlflow/charts/mlflow/Chart.yamlor as a separate HelmChart CR inrelease/ - Update
release/kots-support-bundle.yamlif needed to reference wrapper chart specs
Files touched
applications/mlflow/charts/postgres-support/(new directory, all new files)applications/mlflow/release/kots-support-bundle.yaml(potential update)
PR target
Branch PRs to feat/mlflow-enterprise-patterns (not main).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the patterns/support-bundles pattern and the existing MLflow chart under applications/mlflow/charts/mlflow. Create the listed postgres-support chart files with collectors and analyzer, then verify the dependency or HelmChart integration and inspect release/kots-support-bundle.yaml for any required reference; done means the wrapper chart exposes the PostgreSQL support bundle specs on the target integration branch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, postgresql
- Domain
- databases, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100