Support additional helm parameters

[mcammisa78]

Hi,

we are running werf with something like: werf helm upgrade -i test bitnami/nginx --wait --kube-apiserver https://127.0.0.1:6443 --kube--token xxxxxx

It seems that some parametes are not still supported. Error: unknown flag: --kube-apiserver.

Both the above parameters allow helm installation without any kube config file, we are using them for installing in a segregated kube namespace the helm chart using a service account token.

Is it possibile add those additional flags ?

[distorhead]

Hi! We need to add these flags into werf itself as well, because werf * and werf helm * commands all share the same kube config options. We are going to discuss with the team when we could implement this feature.

BTW, there is kube-config-base64 option, which is available in all werf * commands (werf helm * as well), and which is not available in vanilla helm.

[ilya-lesikov]

werf helm was made obsolete by the Nelm 1.0 release. nelm release install should handle this with all these options:

Kubernetes connection options:
      --kube-api-server=""
          Kubernetes API server address. Vars: $NELM_KUBE_API_SERVER, $NELM_RELEASE_INSTALL_KUBE_API_SERVER
      --kube-api-server-tls-name=""
          The server name for Kubernetes API TLS validation, if different from the hostname of Kubernetes API server. Vars:
          $NELM_KUBE_API_SERVER_TLS_NAME, $NELM_RELEASE_INSTALL_KUBE_API_SERVER_TLS_NAME
      --kube-ca=""
          Path to Kubernetes API server CA file. Vars: $NELM_KUBE_CA, $NELM_RELEASE_INSTALL_KUBE_CA
      --kube-token=""
          The bearer token for authentication in Kubernetes API. Vars: $NELM_KUBE_TOKEN, $NELM_RELEASE_INSTALL_KUBE_TOKEN
      --no-verify-kube-tls=false
          Don't verify TLS certificates of Kubernetes API. Vars: $NELM_NO_VERIFY_KUBE_TLS, $NELM_RELEASE_INSTALL_NO_VERIFY_KUBE_TLS

Try this and report if there is any issue.