Joe Julian

This is easily solved like this: ``` helm install --values

My personal opinions: `#1` provides the least surprise and matches a method that is common throughout the industry. `#2` is confusing and likely to cause mistakes. `#3` is ok, still...

> Also as @sirianni mentioned in the pull request, the plain values.d directory could be considered loaded by default, just like values.yaml That'll probably be considered a breaking change by...

@antgamdia Can you please rebase?

fyi, I did double-check the source. The command you give helm is run from here: https://github.com/helm/helm/blob/main/pkg/postrender/exec.go#L47 There's nothing in there that would tell windows to run it any other way....

This seems to be an upstream problem. Closing. If this problem gets solved upstream and doesn't solve it in helm, please feel free to open a new issue.

Closing for lack of response.

I think it's fair to suggest that the addition of maxSurge be taken into account when determining readiness. I also think that's different topic worthy of it's own issue.

I'm going to go ahead and close this based on [the last response](https://github.com/helm/helm/pull/10831#issuecomment-1460491038).

Thank you for that answer, @omniproc. That is correct and answer's the OP's question. Since this is not a helm issue, but rather an issue with how the chart validation...