Failing to look at gateway cluster when using k8s portforwarding

Deploying Dask
1

I am a newbie to dask and I created a multi user gateway cluster in gke environment. I port forwarded the proxy-public load balancer created by helm.

When I port forward that service and try to use the cluster the cluster connection problem starts.

Am I doing it wrong? What is the best and secure way for other services to create a cluster and use it?

TIA and I am adding the logs below.
E1217 21:50:23.119171 76793 portforward.go:346] error creating error stream for port 8080 → 8000: Timeout occurred
Handling connection for 8080
E1217 21:50:39.878720 76793 portforward.go:368] error creating forwarding stream for port 8080 → 8000: Timeout occurred
E1217 21:50:44.938244 76793 portforward.go:346] error creating error stream for port 8080 → 8000: Timeout occurred
E1217 21:50:47.976801 76793 portforward.go:368] error creating forwarding stream for port 8080 → 8000: Timeout occurred
Handling connection for 8080
E1217 21:51:00.953694 76793 portforward.go:346] error creating error stream for port 8080 → 8000: Timeout occurred
Handling connection for 8080
Handling connection for 8080
E1217 21:51:28.144540 76793 portforward.go:368] error creating forwarding stream for port 8080 → 8000: Timeout occurred
E1217 21:51:32.401303 76793 portforward.go:346] error creating error stream for port 8080 → 8000: Timeout occurred
Handling connection for 8080
E1217 21:52:07.540452 76793 portforward.go:368] error creating forwarding stream for port 8080 → 8000: Timeout occurred

2

Hi @SRAVICHANDRAN,

It seems you have errors when trying to do the port forwarding? Are you sure you have some service available in port 8000 or 8080 in Helm (not an expert here). This really seems a K8S/Helm problem more than a Dask issue.

3

@guillaumeeb Thank you so much for replying. I think the problem is mostly cause of port-forwarding. I could avoid this by adding an internal load balancer in gcp. Now it works well. Thanks again.

1 Like