nerdguru opened a new issue #229: Upon helm execution "an error occurred forwarding 39967 -> 44134" URL: https://github.com/apache/incubator-openwhisk-deploy-kube/issues/229 Hi there, 7 days in, I may be the first person not on the development team to try this out and I'm a helm noob, so keep that in mind. I got through the Helm install and the "Initial setup" cleanly for an attempt at putting OpenWhisk on top of a minikube cluster. For the "Customize the Deployment" section, I first verified that nothing was already listening to 31001 (with netstat -no | grep 31001, which returned nothing) and I substituted my local IP address for the example in mycluster.yaml. First minor thing, the instructions don't tell you to cd into the helm directory, so the first time I tried to run "helm install . --namespace=openwhisk --name=owdev -f mycluster.yaml" in my home directory, helm complained that it couldn't find a Chart.yaml. As a helm noob, I assumed it would traverse my folders until it found one, but I guess not. After cd'ing to the helm directory that contains the Chart.yaml and copying the aforementioned mycluster.yaml into that directory, here's what I get: ``` $ helm install . --namespace=openwhisk --name=owdev -f mycluster.yaml E0620 10:37:57.405197 26380 portforward.go:331] an error occurred forwarding 39967 -> 44134: error forwarding port 44134 to pod 1fe0b89e31e42c806fef7c73a5393f4fcf41d76262e64500e7f1d73c44abc871, uid : unable to do port forwarding: socat not found. Error: transport is closing ``` I have no idea where to start troubleshooting that since none of the ports mentioned are in either the Chart.yaml or the mycluster.yaml. I had a prior OpenWhisk install attempt using the old instructions on this same minikube cluster, but removed all the pods/services/deployments. Not sure if that's impacting what I'm seeing here. Any clues/thoughts? I love the approach you're taking here and look forward to getting it running!
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
