The RKE/k3s kubeconfig should be used for Rancher helm upgrades #130
Description
A kubeconfig for the local cluster can be generated from the Rancher UI. If this is mistakenly used for helm upgrades, the dependency on the Rancher API being available can cause issues - as Rancher pods will be likely re-reployed and prevent the apply of other objects.
An upgrade with this kubeconfig resulted in the below error:
Error: UPGRADE FAILED: cannot patch "rancher" with kind Ingress: an error on the server ("<html>\r\n<head><title>502 Bad Gateway</title></head>\r\n<body>\r\n<center><h1>502 Bad Gateway</h1></center>\r\n<hr><center>openresty/1.15.8.1</center>\r\n</body>\r\n</html>") has prevented the request from succeeding (patch ingresses.extensions rancher)
To prevent this, stating a requirement for upgrades to use the RKE/k3s kubeconfig, which performs a direct kube-apiserver connection.