I have a strange problem. I have

Service/cockroachdb

listening on 26257. I also have a manifest that looks as follows:

kind: Deploy
type: kubernetes
name: cockroach-client
dependencies:
  - run.cockroach-db-confirm
spec:
  files:
    - dev/client.yml
  portForwards:
    ...
    - name: db
      resource: Service/cockroachdb
      targetPort: 26257
      localPort: 26257

I can connect using the

cockroach sql

CLI tool using this port-forward without any issues. However, I'm trying to use a tool called JetBrains Datagrip to connect (over JDBC driver) to localhost:26257. It does not work -- the connection fails (a connection failure, not certs or something else). What's extremely strange to me is that when I manually port-forward using

kubectl port-forward svc/cockroachdb 26257:26257

, it works every time. No issues. I understand that this might actually be a Datagrip limitation, but I wanted to post it here because datagrip is simply a client looking for a valid connection. The fact that the manual port-forward works when the port-forward created by garden does not (at least for this one tool) is perplexing and leaves me with questions about how garden sets up the port forward. I would assume it's just the exact command I wrote out above, but maybe not? Thanks again for your help team.

Hi @fresh-yak-35965 Can you double check if Garden is forwarding to the correct local port? See note this from our docs:

The preferred local port to forward from. If none is set, a random port is chosen. If the specified port is not available, a warning is shown and a random port chosen instead.

If the configured

localPort

is already in use, a random port is chosen. Is it possible that this was the case?

If that were true it would not have let me explicitly

kubectl port-forward

, I think.

Hi @fresh-yak-35965 Can you check with netstat as well if the port is bound on ipv4 and ipv6 when port-forwarding with gardenß

Sure. That's a great idea.

Happy to hear that!