Connecting to external mysql db from nodejs GKE pod

Question

I have a nodejs express app that connects to a mysql DB using:

const dbconfig = {
 client: 'mysql',
 connection: {
     host: config.db.host,
     user: config.db.user,
     password: config.db.password,
     database: config.db.database,
     port: config.db.port,
     charset: 'utf8',
     ssl: {
         ca: fs.readFileSync(__dirname + '/root_ca.pem')
     }
 }
}

In my local docker env this connection is successful, however when deploying this onto a kube cluster I am unable to connect to host:port.

The VPC is set up to allow Ingress/Egress traffic on that host/port.

And a service and endpoint were setup as well:

kind: "Service"
apiVersion: "v1"
metadata:
 name: "mysql"
spec:
 ports:
  - name: "mysql"
    protocol: "TCP"
    port: 13306
    nodePort: 0
selector: {}

---

kind: "Endpoints"
apiVersion: "v1"
metadata:
 name: "mysql"
subsets:
 - addresses:
   - ip: "34.201.17.84"
   ports:
    - port: 13306
      name: "mysql"

Update: Still no luck but more info shows that the pod and the node are not able to reach the host.

what is the error you are getting? do you not have a connection to the server or is it a credential issue? — Amityo
– Amityo, Commented Feb 28, 2019 at 20:33
@Amityo connect EHOSTUNREACH is the error, so the host is unreachable — Chaosjosh
– Chaosjosh, Commented Feb 28, 2019 at 21:10
try to curl the endpoint (use ip + port) from inside a pod and directly from the node to make understand if the issue is outbound traffic or some configuration issue with the endpoint/service — Amityo
– Amityo, Commented Feb 28, 2019 at 21:36
Same error is displayed in curl and telnet, "Host is unreachable" — Chaosjosh
– Chaosjosh, Commented Feb 28, 2019 at 21:39

Chaosjosh · Accepted Answer · 2019-03-14 21:02:40Z

1

So with the help of google support I was able to find a solution to my problem. The issue was that the ip address that is whitelisted to connect to the database was not the ip address of the loadbalancer; as loadbalancers are for ingress traffic and not egress traffic.

The work around for this is to create a private cluster and then route the egress traffic of that cluster through a single ip (or ip range) using Google Cloud NAT service. Once that was done I was able to successfully connect to the DB without the need of the extra endpoints/mysql service.

answered Mar 14, 2019 at 21:02

Chaosjosh

1371 silver badge13 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Connecting to external mysql db from nodejs GKE pod

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related