diff --git a/content/blog/using-aks-and-socks-to-connect-to-a-private-azure-db/index.md b/content/blog/using-aks-and-socks-to-connect-to-a-private-azure-db/index.md index 30b0c2b3..8d03cbf5 100644 --- a/content/blog/using-aks-and-socks-to-connect-to-a-private-azure-db/index.md +++ b/content/blog/using-aks-and-socks-to-connect-to-a-private-azure-db/index.md @@ -22,7 +22,7 @@ tags: author: "Dave Gallant" --- -I ran into a roadblock recently where I wanted to be able to conveniently connect to a managed postgres database within Azure that was not running on public subnets. And by conveniently, I mean that I'd rather not have to spin up an ephemeral virtual machine running in the same network and proxy the connection, and I'd like to use a local client (preferably with a GUI). After several web searches, it became evident that Azure does not readily provide much tooling to support this. +I ran into a roadblock recently where I wanted to conveniently connect to a managed postgres database within Azure that was not running on public subnets. And by conveniently, I mean that I'd rather not have to spin up an ephemeral virtual machine running in the same network and proxy the connection, and I'd like to use a local client (preferably with a GUI). After several web searches, it became evident that Azure does not readily provide much tooling to support this.