Use PrivateDNSZones instead of DNSZones type Private for clusters #2470
Conversation
|
/test e2e-azure |
openshift-ci-robot
added
size/XXL
|
Missing capability for handle Private DNS Zone and its records blocks @jhixson74 Azure bring your own work as the current DNS Zone type |
abhinavdahiya
force-pushed
the
azurer_private_dns
branch
from
7d8a36f to
cc4b318
Compare
|
/test e2e-azure |
|
/retest |
abhinavdahiya
force-pushed
the
azurer_private_dns
branch
from
cc4b318 to
bf046dc
Compare
|
/test e2e-azure |
…ndle private_dns zone
Using the upstream azurerm provider is not possible for now because of following reasons:
1) There is not srv record resource for private dns zone
2) The version of provider that has the private dns zone resources `1.34.0` has a lot of bugs like
* hashicorp/terraform-provider-azurerm#4452
* hashicorp/terraform-provider-azurerm#4453
* hashicorp/terraform-provider-azurerm#4501
Some of these bugs are fixed, and some are in flight.
Another reason moving to `1.36.0` which might have all the fixes we need is the provider has moved to using
`standalone terraform plugin SDK v1.1.1` [1]. Because we vendor both terraform and providers, this causes errors like
`panic: gob: registering duplicate types for "github.com/zclconf/go-cty/cty.primitiveType": cty.primitiveType != cty.primitiveType`
Therefore, we would have to move towards a single vendor for terraform and plugins for correct inter-operation, which is tricker due to conflicts elsewhere
A simple 4 resource plugin that re-uses the already vendored azurerm provider as library and carries over the required resources seems like an easy fix for now.
[1]: hashicorp/terraform-provider-azurerm#4474
Using the Private DNS Zone also allows us to remove our previous hack [1] [1]: openshift@8ac9ab4
the ingress-operator can handle the Private DNS Zone since [1] [1]: openshift/cluster-ingress-operator#300
… deleting public records Updates the destroy to look for both DNS Zones type Private and Private DNS Zones to find the private records and the corresponding DNS Zone type Public. Since the zone name for both types of private dns zone is the same, we can try both to calculate the private records and then re-use the same codepath to delete the public records.
abhinavdahiya
force-pushed
the
azurer_private_dns
branch
from
bf046dc to
65111a0
Compare
|
/test e2e-azure |
|
/retest |
1 similar comment
|
/retest |
|
@abhinavdahiya: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
/test e2e-aws /test e2e-azure |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya, jhixson74 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
terraform/exec/plugins: add embedded 'azureprivatedns' provider to handle private_dns zone
Using the upstream azurerm provider is not possible for now because of following reasons:
There is not srv record resource for private dns zone
The version of provider that has the private dns zone resources
1.34.0has a lot of bugs likeazurerm_image: add option to set the hyper_v_generation for the image hashicorp/terraform-provider-azurerm#4453Some of these bugs are fixed, and some are in flight.
Another reason moving to
1.36.0which might have all the fixes we need is the provider has moved to usingstandalone terraform plugin SDK v1.1.1azurerm-sdk-bump. Because we vendor both terraform and providers, this causes errors likepanic: gob: registering duplicate types for "github.com/zclconf/go-cty/cty.primitiveType": cty.primitiveType != cty.primitiveTypeTherefore, we would have to move towards a single vendor for terraform and plugins for correct inter-operation, which is tricker due to conflicts elsewhere
A simple 4 resource plugin that re-uses the already vendored azurerm provider as library and carries over the required resources seems like an easy fix for now.
data/azure: use azureprivatedns provider to create private records
Using the Private DNS Zone also allows us to remove our previous hack
More information in individual commits.