Problems when the VPC Subnet "primary_dns" attribute is not set to a system DNS address

[ippeter]

Good afternoon!

The VPC Subnet resource (https://github.com/sbercloud-terraform/terraform-provider-sbercloud/blob/master/docs/resources/vpc_subnet.md) marks the "primary_dns" and "secondary_dns" attributes as Optional.

If primary_dns and secondary_dns are really omitted, the subnet will be successfully created indeed, but customers won't be able to create some other resources in this subnet (a CCE cluster, for instance, or access an SFS share), because other resources might require access to internal services, which should be discoverable via the system DNS of 100.125.13.59

So the problem seems to be as follows: if the primary DNS is not set to "100.125.13.59" for a subnet, the creation of some other resources in this subnet will fail.

Could you please consider this issue?

One solution might be to update the documentation for the VPC Subnet resource and mark the importance of 100.125.13.59 Another solution seems be to assign a default value of 100.125.13.59 to "primary_dns"

Sincerely yours, Peter.