Because Azure Database for PostgreSQL is a managed database service, users are not provided host or OS access to view or modify configuration files such as pg_hba.conf. The content of the files is automatically updated based on the network settings.
Applications that are deployed on different subnets within the same virtual network can access flexible servers directly.
So, since our AKS and Postgresql flexible servers are in the same VNet the above assertion holds. Have attached a snapshot of the Networking tab of postgresql server which says the same thing.
Regards
Prabir Sarkar
On Tue, Sep 7, 2021 at 1:51 PM Julien Rouhaud <rjuju123@gmail.com> wrote:
On Tue, Sep 7, 2021 at 4:14 PM Prabir Kr Sarkar <prabir.kr.sarkar@gmail.com> wrote: > > The grafana pod fails to start with the following error: > > t=2021-09-07T06:40:00+0000 lvl=info msg="Connecting to DB" logger=sqlstore dbtype=postgres > t=2021-09-07T06:40:00+0000 lvl=info msg="Starting DB migrations" logger=migrator > service init failed: failed to check table existence: pq: no pg_hba.conf entry for host "10.240.1.45", user "grafana", database "grafana", SSL off
That seems quite self explanatory. Your grafana is trying to connect as "grafana" role, on "grafana" database from 10.240.1.45, and your pg_hba.conf file doesn't allow it. I'm not sure how to configure that on AKS but you need to either authorize it or configure grafana to use some other credentials that are already allowed, like this one:
> Note: - We can however, connect to the postgresql flexible server from a pod (with psql) in the same AKS.
