Helm repo support
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Is your feature request related to a problem? Please describe.
When containers that are part of an existing Helm chart get synced down to Pulp they lose connection to their representative charts.
Describe the solution you'd like
Helm repo support
Describe alternatives you've considered
The single artifact repo didn't really work well for this task
Additional context
https://helm.sh/
https://helm.sh/docs/glossary/
https://chartmuseum.com/
https://chartmuseum.com/docs/#mirroring-the-official-kubernetes-repositories
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 Helm glossary and ChartMuseum mirroring documentation linked in the issue, then examine how pulpcore currently syncs containers into artifact repositories. Define the repository and chart relationship that must be preserved during synchronization; done means Helm repositories retain their representative charts instead of losing that connection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100