Open beasteers opened 1 year ago
I have the same issue. It is intermittent as well, one time it will work, then it won't.
I have the same issue since we moved to split dns on our VPN. This should be fixed if this provider can upgrade to Go 1.20: https://danp.net/posts/macos-dns-change-in-go-1-20/ https://github.com/Telmate/terraform-provider-proxmox/issues/665
@cyrilgdn Are you able to upgrade the Go version, would raising a PR help? Thanks
Just coming back around to this issue. I think this is a duplicate: https://github.com/cyrilgdn/terraform-provider-postgresql/issues/241
I'm going to try and raise a PR.
Running into exact same error on AKS and it started happening two weeks ago. Any ideas?
Essentially, I'm having DNS trouble with the terraform postgres provider. It should probably be using some 10.0.0.10:53 nameserver or something for the internal cluster (?) I think? But instead, it's trying to lookup the postgres service using the LAN dns.
How can I use this provider with a local cluster service name? I would have thought it would work out of the box. I'd prefer not having to expose postgres to the public, but maybe I'm misunderstanding how this works.
Thanks!
Terraform Version
Affected Resource(s)
Please list the resources as a list, for example:
Terraform Configuration Files
Here's the relevant config
Panic Output
Expected Behavior
It should have resolved the postgres address to the internal cluster service and been able to connect
Actual Behavior
It failed using 192.168.1.1:53 instead
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
Important Factoids
I'm deploying to an AKS cluster from a mac