-
Notifications
You must be signed in to change notification settings - Fork 82
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
Prepare upgrade to Terraform azurerm v2.x.x #161
Conversation
Add association resources for routetable-to-subnet and nsg-to-subnet in parallel to internal associations on the subnet resource.
Is this PR dependent to the azurerm version bump in terraformer? In the past we had issue with gardener-attic/gardener-extensions#331 which was reverted in gardener-attic/gardener-extensions#348. Is this now fixed? |
It is only fixed if you keep the inline and external association in parallel. This PR is not related to a bump of Terraform version. It is just a preparation that we can move to azurerm v2 in the future (which we need to proceed with the Nat Gateway story). |
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Add migration to Terraform azurerm provider v2. Add migration for Gardener managed NatGateway public ip. TODO: This require gardener#161
Add migration to Terraform azurerm provider v2. Add migration for Gardener managed NatGateway public ip. TODO: This require gardener#161
Add migration to Terraform azurerm provider v2. Add migration for Gardener managed NatGateway public ip. TODO: This require gardener#161
Add association resources for
routetable-to-subnet
andnsg-to-subnet
in parallel to internal associations on the subnet resource.How to categorize this PR?
/kind impediment
/priority normal
/platform azure
What this PR does / why we need it:
We need to upgrade the
azurerm
Terraform provider to at least version v2.12.0 as this is required for the NatGateway bring your own IP scenario (#54 (comment), hashicorp/terraform-provider-azurerm#6450, hashicorp/terraform-provider-azurerm#6052).As preparation for the upgrade we need to add the
routetable-to-subnet
andnsg-to-subnet
external association resources in parallel to the internal associations on the subnet resource. Otherwise we won't be able to upgrade toazurerm
v2, see here:hashicorp/terraform-provider-azurerm#2358 (comment)
Special notes for your reviewer:
Create a
Infrastructure
without this change. Then checkout this PR and reconcile theInfrastructure
once more. The route table/nsg to subnet association on Azure should not change.Release note: