Troubleshooting
Problem
The Helm Tiller version in ICP 2.1.0.3 has been unknowingly changed from that installed by ICP.
This can happen if the user has configured their command line client with the kubectl commands (from the UI) and then calls helm init without specifying the --client-only flag (or -c which means the same).
Note: The Helm CLI displays a warning message when using helm init (without the --client-only flag) that Tiller was already deployed on the cluster and that the --upgrade flag is needed if you wanted to upgrade Tiller. If you continue with the helm init command using the --upgrade flag it will overwrite the Tiller version installed with ICP
Symptom
Deploying a chart through the Web UI may fail with an error like this:
Internal service error : rpc error: code = Internal desc = connection error: desc = "transport: authentication handshake failed: tls: first record does not look like a TLS handshake
Helm CLI commands may fail with errors about incompatible versions, or connection errors.
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSBS6K","label":"IBM Cloud Private"},"Component":"Helm Tiller","Platform":[{"code":"PF016","label":"Linux"}],"Version":"2.1.0.3: 2.1.0.3 Fix Pack 1","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
12 December 2018
UID
ibm10730087