-
Notifications
You must be signed in to change notification settings - Fork 55
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
Passing args to helm #36
Comments
|
Can you send over the app definition so I can see what you have set? |
Or the helmfile content if you have the args defined there. |
Like I'm using multiple yaml in helmfile.d directory, I don't have a helmfile.yaml.
And my app definition :
|
I suspect this has some behavior difference due to the repository being |
I've opened this: helmfile/helmfile#727 |
Sorry for the delay
|
@travisghansen I have the same issue with oci repositories. I did some investigation and can say: you are always passing this arguments to 'template' command:
So, my suggestion is make this arguments are optional, or add a new ENV to possibility disable this args. |
@welderpb thanks! I'm unaware of another option to ensure proper kubeapi versions etc can be passed down to helm, am I missing something? |
@travisghansen it is not necessary to pass this arguments to helm templating, it is should be optional. |
In many situations they absolutely are required unfortunately :( we’ll work closely with helmfile to make sure we sanely cover the necessary use cases and the issue will go away. |
Hello,
I'm experiencing a strange behavior when I'm using helmfile.d tree structure.
Some args are passed to helm pull command but they shouldn't (cf output below)
It seems passing args from helmfile to helm is not a good practice (doc)
Do you think it could be improved or make it optional ?
For now, I removed the --args parameter from the script like I'm not using it.
The text was updated successfully, but these errors were encountered: