an official helm chart

Open
#5,989 0 comments 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker, go, helm

Research direction

The issue names no files, tests, or entry points. Start by reviewing the existing BuildKit deployment and release structure, then clarify whether the goal is an official Helm chart, a buildkit-operator, or both. Done would require an agreed scope and a maintainable deployment path for GitOps promotion across environments.

Written by the indexing model from the issue text.

Description

area/kubernetes help wanted status/triage
Description

its time

needed for gitops environments driven by technologies such as argocd / kargo, and the ability to promote new versions between stages such as dev -> test -> prod

we can't deploy things into our environments which don't have a helm chart, we'd have to create our own helm chart, an official chart would be much better maintained than for everyone who needs one to reinvent the wheel

or maybe a buildkit-operator which runs things like docker buildx create --bootstrap --name=kube --driver=kubernetes behind the scene, but installed / managed via an official helm chart

Dominant language
Go
Stars
10.3k
Forks
1.5k
Avg merge
1d 23h
Merged PRs (30d)
48

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 moby/buildkit

All issues in moby/buildkit

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.