OpenCut-app / OpenCut-app/OpenCut
Document Kubernetes installation with the HelmForge Helm chart
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 89.8k
- Forks
- 8.9k
- PR merge metrics
- No merged PRs in 30d
Description
Hi maintainers,
I was looking through the project documentation and did not find a Kubernetes installation section using Helm. If I missed an existing official page, please point me to it and feel free to close this.
HelmForge now publishes a production-oriented Helm chart for OpenCut:
- Documentation: https://helmforge.dev/docs/charts/opencut
- Chart source: https://github.com/helmforgedev/charts/tree/main/charts/opencut
The basic installation flow is intentionally simple:
helm repo add helmforge https://repo.helmforge.dev
helm repo update
helm install opencut helmforge/opencut --namespace opencut --create-namespace
The chart is meant to provide a Kubernetes-native path for users who want to run OpenCut on their own clusters, with explicit values, pinned upstream images, and common production surfaces such as persistence, service exposure, probes, security contexts, and optional integrations where applicable.
HelmForge also publishes a public Docker image for OpenCut here:
The chart uses that image so Kubernetes users have a ready-to-pull runtime artifact in addition to the Helm values surface.
Would you be open to adding a short Kubernetes / Helm installation section to the documentation that references this chart as a community-maintained deployment option?
If that direction makes sense, I would be happy to prepare a documentation PR with a concise install section, links to the HelmForge chart documentation, and any wording you prefer around support boundaries.
Contributor guide
No contributing guide indexed for this repository
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 reviewing the existing documentation structure and installation pages to find the appropriate location for a Kubernetes section. Add a concise Helm installation flow using the commands and HelmForge chart documentation link from the issue, and clarify that it is community-maintained with the stated support boundaries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, helm, kubernetes
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100