-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request: Helm3 (i.e. API v2) chart support #14
Comments
Hi, i'm certainly open for this! Will take a look at it this week. |
Awesome! Thank you. It seems the |
@IAXES Might I ask what your use case is, considering you don't need to extend the image? |
@hazcod Mostly personal interest in a hardened Alpine image in general. I'll likely want to make changes to the image (i.e. via the |
FYI, I've been thinking about doing the same for debian. Mostly because the whole security list thing is better maintained compared to alpiine, since it builds upon years of experience. |
As in, creating another project under |
Yep! |
Sounds fun! |
Sorry for the delay @IAXES , but i've been having issues setting up my kubernetes cluster via terraform. |
Good day,
Can we please have support (i.e. via this repo) for a Helm chart?
https://medium.com/@mattiaperi/create-a-public-helm-chart-repository-with-github-pages-49b180dbb417
If there are specific features one wishes to override, it could be done either via CLI parameters or a custom
Values.json
at deployment time, which would provide a preferable alternative to people forking the Dockerfile. If the repo is configured to support it, I'd be happy to contribute to the chart.The text was updated successfully, but these errors were encountered: