vllm-project
[CI] Generate helm package from kubebuilder manifests
🚀 Feature Description and Motivation
Kubebuilder internally uses kustomize to manage installations. However, many users prefer using Helm for managing Kubernetes manifests. Currently, Kubebuilder does not support direct generation of Helm manifests (see discussion).
Given this gap, there are some user practices being employed at the moment. To address this need, we propose building a Helm package for Kubebuilder and later defining the best practices for its usage.
Let's start by creating the Helm package and then refine our approach based on community feedback and best practices.
Use Case
No response
Proposed Solution
No response
/cc @M00nF1sh are you aware of any tools to covert kustomize to helm package? We do not want to maintain the helm separately
@Jeffwan there isn't. we can create a helm chart easily from the kustomized YAMLs though. I can help with that and maybe remove those kustomize templates(so we don't need to maintain support for both)? Also, helm charts can be vended via github pages of this repo
@M00nF1sh Can we add the helm repo first? Let's have a short discussion on the kustomize manifests maintenance later.
kustomization and generate yaml should be good enough for v0.1.0 release. Helm package support can be postponed to v0.2.0
Good news, kubebuilder has added a plugin (currently in alpha) for helm. See here. Might be worth revisiting this issue.
We use helmify in our repo, just provide some information. See https://github.com/InftyAI/llmaz/blob/1c23184eef8b6391dbd36a19e1aae92d46b216f7/Makefile#L309-L311
Hi @kerthcet, I'm a little confused, you are pointing to a different repo "llmaz" instead of "aibrix"? where can i find the helm chart or guidance to convert aibrix to helm chart? Thanks.
What I mean is we can have a try with helmify if possible, then kustomize is the only source, up to now, we don't have problems. But the potential problem is the third-party software maintenance cost.
