Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Public DNS for flexible server private access #89

Open
ohorvath opened this issue Jul 17, 2021 · 0 comments
Open

Feature request: Public DNS for flexible server private access #89

ohorvath opened this issue Jul 17, 2021 · 0 comments

Comments

@ohorvath
Copy link

We deploy PostgreSQL servers for our customers using ARM templates and the public/private implementation for flexible server is very confusing. For single servers we use service endpoints to secure public servers and private endpoints to secure the private ones. With flexible there is no way to restrict the public servers to be allowed from VNET only, IP whitelisting doesn't make any sense. Of course we could use the private access mode to secure the traffic, but the implementation is very complicated. Dedicated subnet and private DNS zone requirements make this task impossible to automate. We can't create subnets or private DNS zones in our customer's subscription just for this purpose.

Please consider to remove the dedicated subnet requirement and implement public DNS support instead of private DNS for private access mode like in AKS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant