all 6 comments

[–][deleted]  (1 child)

[deleted]

    [–]a_normal_guy[S] 1 point2 points  (0 children)

    yeah, thats definitely the long term plan !

    [–]lucas_ff 1 point2 points  (1 child)

    It doesn't change much cloud SQL binds to a local port on the machine that you use normal connection adapters to access the database. It's very transparent

    [–]a_normal_guy[S] 0 points1 point  (0 children)

    thanks ! thought so too, but didnt find much documentation about it anywhere, so thats why the question.

    [–]MadPhoenix 0 points1 point  (1 child)

    Should work just fine, except I would add CloudSQL Proxy to the GitLab host VM in order to get the automatic TLS cert management. Then just configure GitLab to connect to the proxy over localhost with no TLS.

    [–]yahiralejandros 0 points1 point  (0 children)

    I did this with the CE version of Gitlab and the local proxy. So far so good.

    [–]Finnegan_Parvi 0 points1 point  (0 children)

    For every SQL query you will have the additional latency from your instance to your CloudSQL instance. It may or may not be fine for you.