-
Notifications
You must be signed in to change notification settings - Fork 567
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
How to deal with simple kubernetes definitions that don't have a chart #1157
Comments
@Vad1mo Hey! I believe your list is comprehensive. For the last bullet point, have you ever checked out "helm-x"? With that you can extend helm to install a "kustomization" as a ad-hoc chart:
where the |
FYI, you can run helmfile with helm-x by just providing the path to the helm-x binary with |
May be the https://github.com/helm/charts/tree/master/incubator/raw can help? See helmfile example how to deploy raw kubernetes resource - https://github.com/cloudposse/helmfiles/blob/master/releases/oidc-role.yaml |
Thanks. Yes, the raw chart does help. Actually - @Vad1mo has also mentioned about the raw chart in the beginning of this issue :) |
This is more of a questions. There are more and more CRDs in the wild nowdays and they all come with their own CRs that of course don't come with a Chart.
If I want to keep my helm/helmfile workflow what options do I have to use and parametrize vanilla kubernetes deployment descriptors?
This is what comes into my mind if I want to do that with helmfile
❓ What about passing values from helmfile to kubernetes deployment descriptors?
🤔 Overkill for a simple CR
😒 raw helm, kind of same as postsync
What options are also possible to accomplish the same goal?
The text was updated successfully, but these errors were encountered: