Support port-forward address bind with skaffold dev

[matti]

In Kubernetes 1.13

kubernetes/kubernetes#46517

Adds --address flag to port-forward command that allows listening on addresses other then localhost, so that port-forward can ie. be opened to consumers other then residing in local host like running in docker or different machine/vm

usecase: run skaffold dev in google cloud shell (needs 0.0.0.0 binding)

[matti]

well google cloud shell + skaffold won't work currently anyway because of kubernetes/minikube#3392

[tjerkw]

Yeah i need this too, callbacks to the running kubernetes in dev mode are not working from outside services (like payment callbacks). I fix it now by manually also running "kubectl port-forward --address 0.0.0.0"

[javdl]

@matti You can use a remote cluster to deploy, also your container builds can run in a remote cluster or Google Cloud build. No need to run anything in Cloud Shell as far as I can see...? Also, you would not want to run Minikube in Cloud Shell, it is not made for that. Think about the performance... If it would even start up at all.

[matti]

@joostvanderlaan yes I could, but I has training/classroom scenarios in mind

[demisx]

We need this as well, because current port forwarding (v0.31) opens up forwarded port on 127.0.0.1 (localhost) address only and we need it to be on all, so services outside localhost can still connect to the exposed port.

My current workaround in "Docker for Desktop (Mac)" is to define port type as "LoadBalancer":

...
type: LoadBalancer
ports:
  - port: 3000
    targetPort: 3000

[prokher]

@demisx I just wanted to say thank you. Indeed, saying that service must be load balanced (with type: LoadBalancer) makes Skaffold bind it to 0.0.0.0, which helped me to run skaffold dev --port-forward from inside Docker container we use for development.

[tejal29]

@priyawadhwa is this implemented?

[priyawadhwa]

Nope, we don't have support for changing the listening address right now. It could be added to the portForward section of the skaffold config, and then passed in to kubectl port-forward in the code.