-
Notifications
You must be signed in to change notification settings - Fork 68
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
Support Dynamic Port Allocation #64
Comments
This is now GA so it would be awesome if it is supported. |
any update on the feature ? |
Depends on hashicorp/terraform-provider-google#11052 |
@hanikesn it's now released on the provider google. https://github.com/hashicorp/terraform-provider-google/releases/tag/v4.22.0 |
max_ports_per_vm was not included in their latest release |
Please note that by the provider defaulting to false, it will revert DPA that has been enabled by other means. Previous to 4.22 it was possible to enable DPA and this module would ignore the setting. Now it will revert it. |
Having a hardcoded default_value of `false` for the `enableDynamicPortAllocation` property is troublesome, and the upstream default should be used. This was added as part of GoogleCloudPlatform#6022. By hardcoding the default here, any client will explicitly deprogram the dynamic port allocation setting if it is not part of the client configuration. This is causing problems for those clients that have enabled the dynamic port allocation out of band, since the current support is incomplete (not all parameters can be set via Terraform: terraform-google-modules/terraform-google-cloud-nat#64 (comment)). While full support is being added, removing hardcoded defaults allow out-of-band configurations to continue working.
Thanks for merging this. When will it be released? |
…amicPortAllocation Support for the Dynamic Port Allocation feature (tracked in terraform-google-modules/terraform-google-cloud-nat#64 and hashicorp/terraform-provider-google#11052) was initially implemented in GoogleCloudPlatform#6022, but it lacked support for the maxPortsPerVm field. This field is crucial to allow the full configuration to work.
…amicPortAllocation (#6155) Support for the Dynamic Port Allocation feature (tracked in terraform-google-modules/terraform-google-cloud-nat#64 and hashicorp/terraform-provider-google#11052) was initially implemented in #6022, but it lacked support for the maxPortsPerVm field. This field is crucial to allow the full configuration to work.
…amicPortAllocation (hashicorp#6155) Support for the Dynamic Port Allocation feature (tracked in terraform-google-modules/terraform-google-cloud-nat#64 and hashicorp/terraform-provider-google#11052) was initially implemented in hashicorp#6022, but it lacked support for the maxPortsPerVm field. This field is crucial to allow the full configuration to work. Signed-off-by: Modular Magician <[email protected]>
…amicPortAllocation (hashicorp#6155) Support for the Dynamic Port Allocation feature (tracked in terraform-google-modules/terraform-google-cloud-nat#64 and hashicorp#11052) was initially implemented in hashicorp#6022, but it lacked support for the maxPortsPerVm field. This field is crucial to allow the full configuration to work. Signed-off-by: Modular Magician <[email protected]>
…amicPortAllocation (#6155) (#4400) Support for the Dynamic Port Allocation feature (tracked in terraform-google-modules/terraform-google-cloud-nat#64 and hashicorp/terraform-provider-google#11052) was initially implemented in #6022, but it lacked support for the maxPortsPerVm field. This field is crucial to allow the full configuration to work. Signed-off-by: Modular Magician <[email protected]>
…amicPortAllocation (#6155) (#11933) Support for the Dynamic Port Allocation feature (tracked in terraform-google-modules/terraform-google-cloud-nat#64 and #11052) was initially implemented in #6022, but it lacked support for the maxPortsPerVm field. This field is crucial to allow the full configuration to work. Signed-off-by: Modular Magician <[email protected]>
…amicPortAllocation (#6155) Support for the Dynamic Port Allocation feature (tracked in terraform-google-modules/terraform-google-cloud-nat#64 and hashicorp/terraform-provider-google#11052) was initially implemented in #6022, but it lacked support for the maxPortsPerVm field. This field is crucial to allow the full configuration to work. Signed-off-by: Modular Magician <[email protected]>
…amicPortAllocation (#6155) (#777) Support for the Dynamic Port Allocation feature (tracked in terraform-google-modules/terraform-google-cloud-nat#64 and hashicorp/terraform-provider-google#11052) was initially implemented in #6022, but it lacked support for the maxPortsPerVm field. This field is crucial to allow the full configuration to work. Signed-off-by: Modular Magician <[email protected]>
Guys, any updates on this feature? |
@ep4sh This now fully working in the latest release |
@hanikesn I cannot see anything like "enable_dynamic_port_allocation = var.enable_dynamic_port_allocation" here: https://github.com/terraform-google-modules/terraform-google-cloud-nat/blob/master/main.tf When will it be released? Or am I looking somewhere wrong? |
#73 PR-Added dynamic port feature |
Awesome! |
Any update ? PR looks to be stuck. |
@bharathkkb can this be merged? |
It looks like the Dynamic Port Mapping was released as a part of v4.0.0. However, this still didn't include the |
@leeleelou Facing the same issue. Logged #123 |
Raised PR. Let me know your thoughts |
TL;DR
Add support for Cloud Nat Dynamic Port Allocation. The feature is currently in Preview.
Terraform Resources
Detailed design
The text was updated successfully, but these errors were encountered: