Ask questionsHelm error with forwarding ports


I have new clear installation of K8s and then I installed Helm. If I try to install whatever (i.e. mysql) I get this error message: Error: forwarding ports: error upgrading connection: unable to upgrade connection: pod does not exist

# kubectl -n kube-system get pods                                                                                                 
NAME                             READY     STATUS    RESTARTS   AGE
etcd-master                      1/1       Running   2          3h
kube-apiserver-master            1/1       Running   3          3h
kube-controller-manager-master   1/1       Running   3          3h
kube-dns-3913472980-5wj0x        3/3       Running   6          3h
kube-proxy-tmh3k                 1/1       Running   2          3h
kube-proxy-vssfr                 1/1       Running   0          3h
kube-scheduler-master            1/1       Running   3          3h
tiller-deploy-1491950541-5crrg   1/1       Running   0          2h

Next I tried to set port-forwarding but I still get the same error:

# kubectl -n kube-system port-forward $(kubectl -n kube-system get pod -l app=helm -o jsonpath='{.items[0]}') 44134 
error: error upgrading connection: unable to upgrade connection: pod does not exist

K8s and Helm is running on Ubuntu (v16.04) in my VirtualBox. There I have 2 network interfaces. I'm not sure if problem should be there. My networks:

  • enp0s3 - NAT
  • enp0s8 - host only adapter (for connecting to Node01)

It is almost the same problem like issue 1770.


Answer questions mouhsinelonly

Did anyone found a solution to this


Related questions

Error: validation: chart.metadata is required when using --repo - helm hot 4
"Error: Transport is closing" message when attempting to install hot 2
Error: open .helm\repository\cache\local-index.yaml hot 2
"helm dep build" fails if requirements.yaml contains local dependencies and remote one hot 2
Helm upgrade fails the release after adding a new resource hot 2
Error: could not find a ready tiller pod hot 2
Error: apiVersion 'v2' is not valid. The value must be "v1" hot 2
Unable to start Tiller pod, bind address already in use hot 2
Upgrading releases with immutable resources (e.g. persitentVolume) hot 2
helm 3: Not able to push chart to docker hub hot 1
`helm upgrade --recreate-pods` flag should do a soft restart - helm hot 1
Helm3: No 'init', doesn't use existing ~/.helm hot 1
No kind Job is registered for version batch/v1 hot 1
`Error: rendered manifests contain a resource that already exists` but nothing shows up on `helm list --all` - helm hot 1
error calling eq: invalid type for comparison hot 1
Github User Rank List