Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Feature: Publish a helm chart with the manifest build in

Open
#2,680 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go, helm, kubernetes
Domain
cloud, devops, release

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.

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.

Dominant language
Go
Stars
213
Forks
85
Avg merge
1d 10h
Merged PRs (30d)
38

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.

More from operator-framework/operator-controller

All issues in operator-framework/operator-controller

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.