operator-framework / operator-framework/operator-controller
Feature: Publish a helm chart with the manifest build in
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 213
- Forks
- 85
- Avg merge
- 2d 1m
- Merged PRs (30d)
- 38
Description
Hi,
for the non red hat users. Would you mind publish a helm chart in a oci regsitry alongside with the manifest on each release?
If you have no red hat, the olm becomes harder to consume.
Please let me know, if you want or plan to do that or not. I have buiuld a workaround https://gitlab.com/xrow-public/helm-operator-lifecycle-manager so far.
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 tracing how the manifest is built and published for each release, then review the release workflow and the Helm Operator Lifecycle Manager workaround linked in the issue. Define the chart packaging and OCI registry publishing points, with completion meaning a Helm chart containing the manifest is available alongside every release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm, kubernetes
- Domain
- cloud, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100