-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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: Azure High Availability Ports #372
Comments
Is there any chance this feature is scoped for implementation? It's the last piece of my vDC Terraform implementation and saves me creating hundreds of rules on my load balancer in front of next-gen firewalls. |
Hi @justaugustus, Thanks for the issue, but we are unfortunately still waiting on the GO SDK for Azure to support this. |
From our side, we have successfully deployed a Azure Load Balancer with HA Ports with the following configuration : resource "azurerm_lb_rule" "lb_haports_rule" {
backend_port = 0
frontend_ip_configuration_name = "${azurerm_lb.private-lb-gateway.frontend_ip_configuration.0.name}"
frontend_port = 0
loadbalancer_id = "${azurerm_lb.private-lb-gateway.id}"
name = "lb_haports_rule"
protocol = "All"
backend_address_pool_id = "${azurerm_lb_backend_address_pool.gateway_backend_pool.id}"
probe_id = "${azurerm_lb_probe.lb_gateway_probe_fw.id}"
resource_group_name = "${var.resource_group_name}"
} And it's working ! We simply add "All" in protocol. |
@EtienneDeneuve .. Terraform 0.11.8 throws an error when I run the workaround config. The error is resource "azurerm_lb_rule" "lb_haports_rule" {
protocol = "All"
backend_port = 0
frontend_ip_configuration_name = "${azurerm_lb.ilbmain.frontend_ip_configuration.0.name}"
frontend_port = 0
loadbalancer_id = "${azurerm_lb.ilbmain.id}"
name = "lb_haports_rule"
backend_address_pool_id = "${azurerm_lb_backend_address_pool.ILB2PaloAlto.id}"
probe_id = "${azurerm_lb_probe.paloalto_probe.id}"
resource_group_name = "${data.azurerm_resource_group.pa-rg.name}"
} |
Hi, What surprises me is that the referenced issue for the go-sdk is also closed ! |
I'm also getting
Yet if you leave it to "All" and put in a port it moans that it must be set to 0, which then errors.
|
Excellent ! Many thx for taking care !
kt <[email protected]> schrieb am Do., 20. Sep. 2018, 00:08:
… @DYNSOL <https://github.com/DYNSOL>, @lw81 <https://github.com/LW81>,
@asubmani <https://github.com/asubmani>
Additional validation was added to this resource breaking the workaround.
I have opened #1951
<#1951>
to allow 0 for the ports again.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#372 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ATAFNGwAWpmFwBXq5vpgsigut4vSGvn-ks5ucsBXgaJpZM4Povgw>
.
|
Fixed via #1951 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
This issue was originally opened by @robrankin as hashicorp/terraform#16215. It was migrated here as a result of the provider split. The original body of the issue is below.
Microsoft has just announced the Preview availability of a "High Availability Ports" for the Azure Load Balancer:
https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-ha-ports-overview
It's a pretty great addition to the LB, would be extremely useful to have it exposed in Terraform.
The text was updated successfully, but these errors were encountered: