Note: for support questions specific to Helm, please use see the Helm documentation. This repository's issues are reserved for feature requests and bug reports.
I'm submitting a ...
[ ] feature request
Do you want to request a feature or report a bug?
It is kind of a both
What is the current behavior?
To execute any type helm command, weather it requires k8s config file or not, k8s connection is required.
If the current behavior is a bug, please provide parameters either in plain text or with a screenshot
What is the expected behavior?
k8s connection should not be required for "helm package" command and in any case, and should not be required for helm init if --client only is specified.
What is the motivation / use case for changing the behavior?
A user may not have a k8s cluster or has no intention to connect helm with k8s cluster specially in the build pipeline where the only intent is to package a chart and push to helm repo.
Please tell us about your environment and the type of VSTS agent pool you're running the Helm task in:
[ ] Hosted Linux
[ ] Custom build agents
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
no
Note: for support questions specific to Helm, please use see the Helm documentation. This repository's issues are reserved for feature requests and bug reports.
I'm submitting a ...
Do you want to request a feature or report a bug? It is kind of a both
What is the current behavior? To execute any type helm command, weather it requires k8s config file or not, k8s connection is required.
If the current behavior is a bug, please provide parameters either in plain text or with a screenshot
What is the expected behavior? k8s connection should not be required for "helm package" command and in any case, and should not be required for helm init if --client only is specified.
What is the motivation / use case for changing the behavior? A user may not have a k8s cluster or has no intention to connect helm with k8s cluster specially in the build pipeline where the only intent is to package a chart and push to helm repo.
Please tell us about your environment and the type of VSTS agent pool you're running the Helm task in:
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc) no