-
Notifications
You must be signed in to change notification settings - Fork 468
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 for load_balancer_profile #274
Comments
Hello @mielmat You are talking about specify the outbound IPs like described in this doc page ? Could you make an example of the Thanks |
Hello @zioproto, I'm not sure what kind of configuration should I provide, but what it is missing from my side is possibility to assign ...
load_balancer_sku = var.load_balancer_sku
load_balancer_profile = var.load_balancer_profile
... in this module. |
@mielmat can you propose a PR with this change ? You need to add Define the variables: Validate that You can also add an example: That will run an e2e test, where you create a public IP with Terraform: and you pass it in the If you can draft a PR I will be happy to review it. Thanks |
Sure, I will try to raise PR for that. |
This is a much-needed feature. I have a situation when deploying "ingress-nginx" with dynamic IP or a static IP the load balancer gets assigned this IP for incoming traffic and the initially given IP address for aks is configured as the outgoing rule. |
Considering the PR is merged, when can we expect a release? |
hello @mazilu88 @lonegunmanb we can close this issue because the PR #277 is merged |
Is there an existing issue for this?
Description
Hello,
I would like to know if there is a possibility to extend this module and make load balancer configuration exposed to variable? That would help a lot with a bit more specific cases, like to use already existing public IP to avoid recreation it in case of cluster recreation. This is exposed in
azurerm_kubernetes_cluster
resource, but this module didn't expose that.New or Affected Resource(s)/Data Source(s)
azurerm_kubernetes_cluster
Potential Terraform Configuration
No response
References
No response
The text was updated successfully, but these errors were encountered: